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 the plan and get sign-off before implementing — but right-size the ceremony to the issue: - **Small, well-scoped** (a few files, an obvious approach): a one-line plan and a quick confirm. If the path is genuinely unambiguous, state your assumption and proceed without waiting — the global "bias toward action" rule applies. - **Complex or ambiguous** (multiple subsystems, design choices, real risk): present a full implementation plan and wait for explicit approval before proceeding. When unsure which applies, treat it as complex and ask. ### Step 4: Create or reuse branch, then implement - Check the current branch first: `git branch --show-current` - **If already on a feature branch for this issue** (named `<prefix>/gh-$ARGUMENTS-......