resolve-issue

# Resolve GitHub Issue Systematically resolve GitHub issues with a structured workflow. ## Your task Track your progress through the 6 steps below. Report completion of each step before moving to the next. ### Step 1: Get issue details - Run `gh issue view $ARGUMENTS` to get issue details - Extract title, description, labels, and comments - Identify complexity and scope ### Step 2: Research and understand - Search related PRs: `gh pr list --search "fix issue $ARGUMENTS"` - Search codebase for relevant files and patterns - Review similar issues if applicable ### Step 3: Plan solution - Break the issue into small, manageable tasks - Identify files that need changes - Consider edge cases and testing requirements **CHECKPOINT**: Present implementation plan to user and ask for approval before proceeding. ### Step 4: Create branch and implement - Determine the branch prefix from the issue's type label (see Branch Naming below) - Create feature branch: `git switch -c <prefix>/gh-$ARGUMENTS-<short-description>` - Verify branch: `git branch --show-current` - Implement with frequent commits (see commit strategy below) - **Do NOT include issue references** in commit messages **Commit Strategy:** - Commit every major component — don't wait until everything is done - Each commit must be working code - Typical range: 3-8 commits for most issues - Track which acceptance criteria from the issue have been satisfied as you go ### Step 5: Verify solution - Run `git log --oneline...