메뉴
Create a git branch named after a GitHub issue.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| title | branch-from-issue |
| name | branch-from-issue |
| description | Create a git branch named after a GitHub issue. |
| disable-model-invocation | true |
| argument-hint | [issue-number] [branch-prefix] |
| arguments | ["issue","prefix"] |
| allowed-tools | Bash(gh issue view *) Bash(git checkout *) Bash(git branch *) |
Run:
gh issue view $issue
Extract the issue title from the output. If the issue does not exist or gh is not authenticated, stop and report the error.
Convert the issue title to a branch-safe slug:
Examples:
fix-login-page-crash-on-mobileadd-support-for-oauth-20-pkce-flowupdate-readme-with-installationIf $prefix is not empty, use it as provided.
If $prefix is empty, use feature as the default prefix.
Valid examples: feature, fix, chore, hotfix. Accept any non-empty string the user provides.
Construct the full branch name: $prefix/$issue-<slug>
For example, if $prefix is fix, $issue is 142, and the slug is login-page-crash-on-mobile:
fix/142-login-page-crash-on-mobile
Run:
git checkout -b $prefix/$issue-<slug>
If the branch already exists, report the conflict and stop. Do not force-create or checkout the existing branch automatically.
Report the new branch name and confirm the current branch has switched:
git branch --show-current
Example output:
Created and switched to: fix/142-login-page-crash-on-mobile
Explains code in plain language for someone unfamiliar with the programming language. Use when asked to explain code, walk through logic, describe what a function does, or when the user says "explain this" or "walk me through this".
Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.
Explains what a skill is and demonstrates that skills are working. Use when testing skills, when asked about skills, or when asked to demonstrate how skills work.
Demonstrates the personal scope for Claude Code skills. Use when testing personal-scoped skills or when the user wants to understand the difference between personal and project skill scopes.
Lists the conventions for this project and demonstrates the project scope for Claude Code skills. Use when asked about project conventions, code style, or as a demonstration of project-scoped skills.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.