Learn-skills.dev implement-issue
Use when given a GitHub issue number and base branch to implement end-to-end
install
source · Clone the upstream repo
git clone https://github.com/NeverSight/learn-skills.dev
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/NeverSight/learn-skills.dev "$T" && mkdir -p ~/.claude/skills && cp -r "$T/data/skills-md/aaddrick/claude-desktop-debian/implement-issue" ~/.claude/skills/neversight-learn-skills-dev-implement-issue && rm -rf "$T"
manifest:
data/skills-md/aaddrick/claude-desktop-debian/implement-issue/SKILL.mdsource content
Implement Issue
End-to-end issue implementation via orchestrator script.
Announce at start: "Using implement-issue to run orchestrator for #$ISSUE against $BRANCH"
Arguments:
— GitHub issue number (required)$1
— Base branch name (required)$2
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
| 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/:
— main logorchestrator.log
— per-stage Claude outputstages/
— parsed outputs (tasks.json, etc.)context/
— final status snapshotstatus.json
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.