agentleFS
pjordanandrsnpjordanandrsn/claude-desktop-asahi/.claude/skills/implement-issue/SKILL.md

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

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.
  • ravihammondSkill

    review-issue

    Review and repair one GitHub issue implementation in the current checkout.

    Also in 4 projects that use this

  • sahinSkill

    create-issue

    Also in 6 projects that use this

  • TermiX-officialSkill

    merge-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

  • ShopifySkill

    triage-issue

    Triage a GitHub issue — classify priority (P0/P1/P2), search for duplicates, and apply labels.

    Also in 3 projects that use this

  • SentrySkill

    create-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

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

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
  1. Very specific:

    Check progress via status.json:

    line 38

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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_BRANCH

Or with explicit agent override:

.claude/scripts/implement-issue-orchestrator.sh \
  --issue $ISSUE_NUMBER \
  --branch $BASE_BRANCH \
  --agent patch-engineer

Monitoring

Check progress via status.json:

jq . status.json

Watch live:

watch -n 5 'jq -c "{state,stage:.current_stage,task:.current_task,quality:.quality_iterations}" status.json'

Stages

StageAgentDescription
setupdefaultfetch, worktree, research, evaluate, plan
implementper-taskexecute each task from plan
task-reviewspec-reviewerverify task achieved goal
fixper-taskaddress review findings
simplifycdd-code-simplifierclean up code
testbats-test-validatorrun test suite (shellcheck + BATS)
lintdefaultrun shellcheck and actionlint
reviewcode-reviewerinternal code review
prdefaultcreate/update PR
spec-reviewspec-reviewerverify PR achieves issue goals
code-reviewcode-reviewerfinal code quality check
completedefaultpost summary

Schemas

Located in .claude/scripts/schemas/implement-issue-*.json

Logging

Logs written to logs/implement-issue/issue-N-timestamp/:

  • orchestrator.log — main log
  • stages/ — per-stage Claude output
  • context/ — parsed outputs (tasks.json, etc.)
  • status.json — final status snapshot

Exit Codes

CodeMeaning
0Success, PR created and approved
1Error during a stage
2Max iterations exceeded
3Configuration/argument error

Agent Selection

Tasks are assigned to specialist agents based on the issue type:

AgentUse For
patch-engineerMinified JS patches in build.sh, sed/regex patterns
packaging-specialist.deb, .rpm, AppImage packaging, control files
electron-linux-specialistBrowserWindow, Wayland/X11, DBus tray, native theme
ci-workflow-architectGitHub Actions workflows, release automation
bash-script-craftsmanShell scripts, launcher, build system

Integration

Called by handle-issues via batch-orchestrator.sh.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.