| name | fix-issue |
| version | 2.4.0 |
| description | Fix a GitHub issue following project coding standards. Creates branch, implements fix with TDD, and prepares PR. |
| trigger | manual |
| depends-on | [] |
| references | [] |
| disable-model-invocation | true |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Bash, Edit, Write |
| argument-hint | <issue-number> |
fix-issue
Fix GitHub issue $ARGUMENTS following project coding standards.
1. Get Issue Details
gh issue view $ARGUMENTS
2. Understand the Problem
- Read the issue description carefully
- Check for related issues or PRs
- Identify acceptance criteria
3. Create Feature Branch
Detect the default branch dynamically:
DEFAULT_BRANCH=$(grep -oP '^\- \*\*Default branch:\*\* \K\S+' CLAUDE.md 2>/dev/null)
if [ -z "$DEFAULT_BRANCH" ]; then
DEFAULT_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@')
fi
if [ -z "$DEFAULT_BRANCH" ]; then
for branch in main master develop; do
if git show-ref --verify --quiet "refs/heads/$branch"; then DEFAULT_BRANCH="$branch"; break; fi
done
fi
git checkout $DEFAULT_BRANCH
git pull origin $DEFAULT_BRANCH
git checkout -b fix/issue-$ARGUMENTS
Note: This skill is a standalone quick-fix flow (issue → branch → TDD fix → PR). For fixes that are part of an active sprint, use /story-cycle instead — it integrates with the sprint branch and quality gates.
4. Search for Relevant Code
- Use Glob and Grep to find related files
- Understand the current implementation
- Identify what needs to change
- Check
docs/adr/ for accepted decisions that constrain the fix approach — the fix must respect existing architectural decisions
