fix-issue

---

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

5. Implement Fix (TDD)

1. Write a failing test that reproduces the issue
2. Verify the test fails for the right reason
3. Implement the minimal fix
4. Verify the test passes
5. Run full test suite (use project's test command from CLAUDE.md)

6. Verify Fix

• Ensure code passes linting and type checking
• Review changes for quality

7. Commit and Push

git add .
git commit -m "$(cat <<'EOF'
fix: resolve issue #$ARGUMENTS

[Description of what was fixed and how]

Closes #$ARGUMENTS

Co-Authored-By: Claude <[email protected]>
EOF
)"
git push -u origin fix/issue-$ARGUMENTS