implement-github-issue

Implement GitHub issues end-to-end on dedicated branches with tests, CI mirroring, and pull requests.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/docktermj/senzing-bootcamp-claude-plugin-development --skill implement-github-issue-docktermj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-github-issue
Source: https://github.com/docktermj/senzing-bootcamp-claude-plugin-development/tree/main/.claude/skills/implement-github-issue
Command: npx skills add https://github.com/docktermj/senzing-bootcamp-claude-plugin-development --skill implement-github-issue-docktermj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a GitHub issue into a reviewed pull request involves many error-prone steps: assessing whether the issue is actionable, clarifying ambiguities, choosing an implementation approach, writing tests, matching CI locally, and documenting decisions. This Skill automates that entire workflow while keeping a human in control at two approval gates. ## Core Features & Use Cases - Readiness assessment and clarification: Scores the issue against a six-dimension rubric (goal, acceptance, scope, locus, testability, compatibility), asks batched clarifying questions, and posts the consolidated Q&A to the issue. - Approach selection with optional racing: Implements straightforward changes directly, or races 2-3 competing implementations in isolated git worktrees judged against a pre-written rubric for complex work. - Tests, CI mirror, and guarded delivery: Writes tests matching the repo's existing conventions, replays the GitHub Actions workflow commands locally, then pushes and opens a PR only after explicit approval. It never merges and never commits to main. - Resumable state tracking: Persists per-issue state files so an interrupted run can resume from the exact phase it reached without double-posting comments. - Use Case: Invoke with an issue number to have the Skill branch, implement, test, mirror CI, and open a pull request that closes the issue, posting exactly four structured comments along the way. ## Quick Start Ask the assistant to implement GitHub issue number 42 end-to-end on a new branch and open a pull request for review.

Frequently Asked Questions about implement-github-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a GitHub issue automatically with Claude Code?

Invoke /implement-github-issue with an issue URL, owner/repo#number shorthand, or a bare issue number. The Skill branches, assesses readiness, implements, tests, mirrors CI locally, and opens a pull request after two approval gates.

How does the skill decide between direct implementation and competing approaches?

It races 2-3 isolated worktree implementations when the change spans multiple modules, touches public APIs or schemas, lacks an existing repo pattern, is concurrency or migration sensitive, or the issue proposes multiple options. Otherwise it implements directly.

Can the skill merge pull requests or push to main?

No. It never runs gh pr merge, never commits to main, never force-pushes, and never deletes branches it did not create. It stops at two approval gates and only pushes after explicit user confirmation.

What happens if an issue is invalid, duplicate, or already fixed?

The Skill stops, posts a comment on the issue explaining the evidence, deletes nothing, and reports back to the user. It treats an unnecessary pull request as worse than no pull request.

Can an interrupted issue implementation run be resumed?

Yes. A per-issue JSON state file records the branch, phase, approvals, and posted comments. On restart the Skill offers to resume from the last recorded phase without double-posting issue comments.