implement-issue
Skill1 starsChanged 6 months agoApache-2.0View on GitHub
Use when given a GitHub issue number and base branch to implement end-to-end
31 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- ShipfoxHQ/shipfoxtheir own version, first seen Nov 15, 2026
- kbourzayq/arch-guardtheir own version, first seen Nov 8, 2026
- normalled/apijacktheir own version, first seen Nov 8, 2026
- solo-ist/prosetheir own version, first seen Nov 8, 2026
- gymcoach-app/gymcoachtheir own version, first seen Oct 26, 2026
- Julien-Au/gymcoachtheir own version, first seen Oct 26, 2026
Used with
Projects with it also use review-issue, create-issue and 4 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ravihammondSkillreview-issue
Review and repair one GitHub issue implementation in the current checkout.
Also in 4 projects that use this
sahinSkillcreate-issue
Also in 6 projects that use this
TermiX-officialSkillmerge-pr
Merge a GitHub PR via squash after /preparepr. Use when asked to merge a ready PR. Do not push to main or modify code. Ensure the PR ends in MERGED state and clean up worktrees after success.
Also in 3 projects that use this
ShopifySkilltriage-issue
Triage a GitHub issue — classify priority (P0/P1/P2), search for duplicates, and apply labels.
Also in 3 projects that use this
SentrySkillcreate-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
Also in 5 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 projects that use this
Other versions31 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- aaddrick/claude-pipeline★ 12846% same
Wrote their own version · 30
- dlt-hub/dlt★ 6.1ksame name
- google/site-kit-wp★ 1.4ksame name
- luainkernel/lunatik★ 612same name
- warpdotdev/oz-for-oss★ 316same name
- codemonkey85/PKMDS-Blazor★ 241same name
- gymcoach-app/gymcoach★ 187same name
- Julien-Au/gymcoach★ 187same name
- ShipfoxHQ/shipfox★ 87same name
- dativo-io/talon★ 18same name
- alexjbarnes/cockpit★ 17same name
20 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- improvement-loopSkill
- lintSkill
- setup-build-toolsSkill
- simplifySkill
- triageSkill
- writing-agentsSkill
- writing-skillsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 30 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 38
Check progress via status.json:
“Common” is measured: kept by at least 6 in 10 of the 30 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Implement Issue
End-to-end issue implementation via orchestrator script.
Announce at start: "Using implement-issue to run orchestrator for #$ISSUE against $BRANCH"
Arguments:
$1— GitHub issue number (required)$2— Base branch name (required)
Invocation
Immediately launch the orchestrator:
.claude/scripts/implement-issue-orchestrator.sh \
--issue $ISSUE_NUMBER \
--branch $BASE_BRANCHOr with explicit agent override:
.claude/scripts/implement-issue-orchestrator.sh \
--issue $ISSUE_NUMBER \
--branch $BASE_BRANCH \
--agent patch-engineerMonitoring
Check progress via status.json:
jq . status.jsonWatch live:
watch -n 5 'jq -c "{state,stage:.current_stage,task:.current_task,quality:.quality_iterations}" status.json'Stages
| Stage | Agent | Description |
| setup | default | fetch, worktree, research, evaluate, plan |
| implement | per-task | execute each task from plan |
| task-review | spec-reviewer | verify task achieved goal |
| fix | per-task | address review findings |
| simplify | cdd-code-simplifier | clean up code |
| test | bats-test-validator | run test suite (shellcheck + BATS) |
| lint | default | run shellcheck and actionlint |
| review | code-reviewer | internal code review |
| pr | default | create/update PR |
| spec-review | spec-reviewer | verify PR achieves issue goals |
| code-review | code-reviewer | final code quality check |
| complete | default | post summary |
Schemas
Located in .claude/scripts/schemas/implement-issue-*.json
Logging
Logs written to logs/implement-issue/issue-N-timestamp/:
orchestrator.log— main logstages/— per-stage Claude outputcontext/— parsed outputs (tasks.json, etc.)status.json— final status snapshot
Exit Codes
| Code | Meaning |
| 0 | Success, PR created and approved |
| 1 | Error during a stage |
| 2 | Max iterations exceeded |
| 3 | Configuration/argument error |
Agent Selection
Tasks are assigned to specialist agents based on the issue type:
| Agent | Use For |
| patch-engineer | Minified JS patches in build.sh, sed/regex patterns |
| packaging-specialist | .deb, .rpm, AppImage packaging, control files |
| electron-linux-specialist | BrowserWindow, Wayland/X11, DBus tray, native theme |
| ci-workflow-architect | GitHub Actions workflows, release automation |
| bash-script-craftsman | Shell scripts, launcher, build system |
Integration
Called by handle-issues via batch-orchestrator.sh.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

