메뉴
Fix a GitHub issue by number. Reads the issue, implements a fix, and prepares a commit.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
| title | fix-issue |
| name | fix-issue |
| description | Fix a GitHub issue by number. Reads the issue, implements a fix, and prepares a commit. |
| disable-model-invocation | true |
| argument-hint | ["issue-number"] |
| allowed-tools | Bash(gh issue view *) Bash(gh issue list *) Read Grep Glob |
Run:
gh issue view $ARGUMENTS
If the issue does not exist or the gh CLI is not authenticated, stop and report the error. Do not proceed.
From the issue output, identify:
If the issue is unclear or underspecified, state the assumptions you are making before proceeding.
Search for code related to the issue:
grep -r to find files referencing the relevant function, component, or error messageMake the smallest change that correctly addresses the issue. Follow the existing code patterns in the affected file:
If the codebase has tests:
package.json or the nearest test configuration file)If you cannot determine the test runner, note that and ask the user.
Stage the changes and write a commit message in this format:
fix: <short description matching the issue title>
Fixes #$ARGUMENTS
Do not commit automatically. Present the staged diff and the proposed commit message, then wait for the user to confirm or adjust before committing.