implement-issue

Installation
SKILL.md

Implement Issue

Implement exactly one GitHub issue in the current checkout. Stay local: do not create worktrees, Docker containers, branches, pull requests, labels, issue comments, pushes, or issue closes.

Intake

  1. Require exactly one GitHub issue number from the user. If it is missing or ambiguous, ask for the issue number and stop.
  2. Read repository instructions before editing: root AGENTS.md, nested AGENTS.md files that apply to touched paths, and any domain or issue-tracker docs those files name.
  3. Fetch the issue packet with gh issue view <number> --comments. Also fetch labels or structured fields if needed to understand status.
  4. Search the issue body and comments for parent PRD references. Fetch every referenced parent PRD issue with gh issue view <number> --comments.
  5. Work on the current branch only. Do not create or switch branches.
  6. Infer the base branch from a user-provided base, the branch upstream, or the repository default branch.
  7. Before writing, run git status --short, git log --oneline <base>..HEAD, and inspect any existing diff from <base>...HEAD. Continue partial work already present; do not restart or redo completed work.

Intake is complete when the issue packet, parent PRD context, repo instructions, base branch, working-tree state, and existing branch changes are understood.

Scope

Installs
7
GitHub Stars
1
First Seen
Jun 30, 2026
implement-issue — ravihammond/skills