/resolve-issue

Full issue workflow — fetch details, research, plan solution, implement, and verify.

BOOST

joshukraine@joshukraine

GitHub

From plugin

joshukraine-dotfiles

42924 skills

Install

$ npx -y skills add joshukraine/dotfiles --skill resolve-issue --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/resolve-issue

Context preview

The summary Claude sees to decide when to auto-load this skill.

Full issue workflow — fetch details, research, plan solution, implement, and verify.

SKILL.md

resolve-issue.SKILL.md

name: resolve-issue
description: Full issue workflow — fetch details, research, plan solution, implement, and verify.
argument-hint: "[issue-number]"

Resolve GitHub Issue

Take a GitHub issue through to a verified, committed implementation on a feature branch — stopping short of the PR.

Fetch — both calls, always

gh issue view $ARGUMENTS                # title, labels, body, and a `comments: N` count
gh issue view $ARGUMENTS --comments     # the thread — this one omits the body, so it is not a swap for the first

**Read the comments, not just the body.** The body is the oldest artifact on an issue; comments carry scope added later, sequencing against other issues, and decisions that supersede an acceptance criterion still written in the body. An issue filed months ago and worked today is the normal case, not the exception. Run the second call unconditionally — the `comments: N` count sits in a metadata header that is easy to skim past, and a zero-comment issue costs one wasted call.

Plan before implementing

Right-size the ceremony to the issue:

**Small and well-scoped** (a few files, an obvious approach) — state the plan in a line and proceed. Don't wait for a reply.
**Complex or ambiguous** (multiple subsystems, design choices, real risk) — present the implementation plan and **wait for explicit approval**.

When unsure which applies, treat it as complex and ask.

Branch

Check `git branch --show-current` first:

**Already on a feature branch for this issue** (`<prefix>/gh-$ARGUMENTS-…`) — reuse it, do not create a second branch. This includes re-entering this step inside an autopilot fan-out worktree.
**Otherwise** — `git switch -c <prefix>/gh-$ARGUMENTS-<short-description>`

The prefix comes from the issue's type label. If the project defines its own branch convention, that wins.

| Type label | Prefix | | --- | --- | | `feat` | `feat/` | | `fix` | `fix/` | | `chore` | `chore/` | | `docs` | `docs/` | | `test` | `test/` |

No type label? Bug fixes are `fix/`, new functionality `feat/`, everything else `chore/`.

Commit as you go

Commit each working component rather than everything at the end — typically 3–8 commits for an issue, each one working code.

**Never reference the issue number in a commit message.** Issues close when the PR merges, so the closing keyword belongs in the PR description, not the commits.

Before reporting done

Run the project's full test suite and confirm no regressions. **Do not proceed until it passes.**

Then check off the acceptance criteria the work satisfied. Round-trip through a file rather than a shell variable — issue bodies routinely contain backticks and `$(...)`, and a file keeps them out of shell parsing entirely:

gh issue view $ARGUMENTS --json body --jq '.body' > <scratchpad>/issue-body.md
# edit that file: flip `- [ ]` to `- [x]` for the criteria now satisfied
gh issue edit $ARGUMENTS --body-file <scratchpad>/issue-body.md

Check off only what the work actually satisfied. If a criterion was superseded by a comment, say so in the summary rather than silently ticking or skipping it.