fix-issue

name	fix-issue
description	Take an issue from GitHub or GitLab, implement the fix, verify it, and open a PR/MR. Detects the host from the git remote. Invoke manually with /fix-issue <number-or-url>.
disable-model-invocation	true

/fix-issue $ARGUMENTS

End-to-end: issue → fix → verified change → PR/MR.

Steps

1. Detect host: git remote -v.
   • GitLab → glab issue view $ARGUMENTS, and later glab mr create.
   • GitHub → gh issue view $ARGUMENTS, and later gh pr create.
2. Understand the issue. Read the description and comments. Restate the problem and the acceptance criteria in one or two lines. If it's ambiguous, ask before coding.
3. Locate the relevant code — delegate to the explore subagent to keep context lean.
4. Reproduce first when it's a bug: write a failing test (hand to test-engineer) or a minimal repro so the fix is provably correct.
5. Branch. Create a descriptive branch (e.g. fix/<issue>-short-slug).
6. Implement the fix (delegate to implementer for anything non-trivial). Smallest change that addresses the root cause.
7. Verify. Run tests/lint/build. Show passing output.
8. Review. Have code-reviewer check the diff in a fresh context.
9. Open PR/MR via the /open-pr flow, referencing the issue so it auto-links/closes.
10. Return the URL.

Guardrails

• Don't close the issue manually; let the PR/MR reference do it on merge.
• Never force-push; never commit secrets.