GitHub Issue Start

VerifiedSafe

Start working on a GitHub issue by creating a branch, adding wip label, and fetching latest changes.

Sby Skills Guide Bot
DevelopmentBeginner
7/23/2026
Claude Code
#github-issues#git-branching#workflow#worktree#automation

Recommended for

Automated summary

This skill kicks off work on a GitHub issue by creating and checking out a feature/<number>-<slug> branch from main, after applying a wip label to prevent duplicate work.

Strengths

  • Automatically adds the `wip` label and aborts if another agent is already working on the issue
  • Derives a consistent branch name (feature/<number>-<slug>) from the issue title
  • Fetches `origin/main` before branching so the work starts from an up-to-date base
  • Runs as a single command and prints a readable report of each step

Limitations

  • Assumes the `gh` CLI is installed and authenticated and that the repo uses a `wip` label
  • Has no closing step: the `wip` label is never removed when the task ends
  • Expects the default branch to be `main` and relies on pre-created worktrees (fixed slot layout)
When to use it

Use it at the start of each GitHub issue to claim the work and create the matching feature branch.

When not to use it

Avoid it on repos without a configured `gh` CLI or `wip` label, or whose main branch is not named `main`.

Security analysis

Safe
Quality score82/100

The skill only uses the declared git and gh commands: fetching main, creating/checking out a feature branch, viewing an issue, and adding a wip label. There is no destructive action, no credential or secret handling, no network exfiltration beyond normal GitHub CLI usage, and no obfuscated payloads. The only remote mutation is a benign issue label add.

No concerns found

How this analysis is made

Examples

Start issue #9
/issue-start 9
Claim a feature ticket
/issue-start 42 — start work on the MAC learning / FDB implementation issue
Start a bug ticket
/issue-start 118

name: issue-start description: GitHub Issueの作業を開始する。ブランチを作成してチェックアウト。「/issue-start 4」のように使用 allowed-tools: Bash(git:), Bash(gh:)

Issue Start

Instructions

  1. 引数でIssue番号を受け取る(例: /issue-start 4)
  2. gh issue view <number> --json title,labels でIssueタイトルとラベルを取得
  3. wip ラベルがあれば警告して中止(既に別のClaude Codeが作業中)
  4. タイトルからslugを生成(小文字、スペースをハイフンに、記号削除)
  5. git fetch origin main でmainを最新に取得
  6. gh issue edit <number> --add-label wip でラベル追加
  7. git checkout -b feature/<number>-<slug> origin/main でブランチ作成・切り替え
  8. 作業開始を報告

注意

  • 固定スロット方式: worktreeは事前に作成済み(ruster-1〜5)
  • 各worktreeでClaude Codeを起動して、このスキルでブランチ切り替え
  • wipラベルで重複作業を防止

Example

/issue-start 9

実行結果:

Issue #9 "MAC学習・FDB実装" の作業を開始します

✓ wip ラベルを追加
✓ ブランチ作成: feature/9-mac-fdb

作業を開始してください

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/github-issue-start-mrx3xytc/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/github-issue-start-mrx3xytc' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/github-issue-start-mrx3xytc/download' --output '.skill-downloads/github-issue-start-mrx3xytc/SKILL.md.part' && mv '.skill-downloads/github-issue-start-mrx3xytc/SKILL.md.part' '.skill-downloads/github-issue-start-mrx3xytc/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash(git:*), Bash(gh:*)

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/github-issue-start-mrx3xytc/SKILL.md' && test -s '.skill-downloads/github-issue-start-mrx3xytc/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/issue-start' && cp -R '.skill-downloads/github-issue-start-mrx3xytc' '.claude/skills/issue-start'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/github-issue-start-mrx3xytc'

openskills read 'github-issue-start-mrx3xytc'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/github-issue-start-mrx3xytc/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills