fix

Context

• Repository: !git remote get-url origin 2>/dev/null || echo "no remote"
• Current branch: !git branch --show-current
• Working tree clean: !git status --porcelain | head -5 | wc -l | xargs -I{} sh -c 'if [ {} -eq 0 ]; then echo "yes"; else echo "no — {} uncommitted changes"; fi'

Issue to Fix

URL: $ARGUMENTS

Workflow

Follow these phases in order. Do NOT skip phases or advance without user approval.

Phase 1: Fetch Issue

1. Validate the argument. It must be a GitHub Issue URL matching https://github.com/{owner}/{repo}/issues/{number}. If invalid, STOP and ask for a valid URL.
2. Extract owner, repo, and issue number from the URL.
3. Fetch the issue:

   gh issue view {number} --repo {owner}/{repo} --json title,body,labels,comments,assignees,milestone,state
   

   If the issue is closed, warn the user and ask whether to proceed.
4. Summarize to the user: title, labels, reproduction steps, expected vs actual behavior, error messages, and relevant comments. Flag any mentions of other repositories.
5. Check for linked PRs or duplicates referenced in the body or comments.

Phase 2: Branch

1. If there are uncommitted changes, warn and suggest stashing.
2. Create a fix branch: git checkout -b fix/issue-{number}-{slug} (slug: 3-4 lowercase hyphenated words from the title).
3. Confirm branch creation.

Phase 3: Explore

1. Start from clues in the issue: error messages, file paths, function names, stack traces.
2. Widen if needed: keyword search, git log --oneline -20 -- {path}, related test files.
3. Build the picture: which files, what's wrong, what's correct, localized or cross-cutting.

If exploration exceeds 10 minutes without a clear picture, STOP and present findings. This limit is intentionally tighter than the global 15-minute limit — a single issue should converge faster or needs user guidance.