Use when given a GitHub issue number and base branch to implement end-to-end
Scanned 9/4/2026
Install to Claude Code
npx -y skills add NeverSight/skills_feed --skill implement-issue --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Implement Issue?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/neversight-implement-issue)More formats (shields.io, HTML) on the badges page.
---
name: implement-issue
description: Use when given a GitHub issue number and base branch to implement end-to-end
argument-hint: "[issue-number] [base-branch]"
---
# 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:
```bash
.claude/scripts/implement-issue-orchestrator.sh \
--issue $ISSUE_NUMBER \
--branch $BASE_BRANCH
```
Or with explicit agent override:
```bash
.claude/scripts/implement-issue-orchestrator.sh \
--issue $ISSUE_NUMBER \
--branch $BASE_BRANCH \
--agent patch-engineer
```
## Monitoring
Check progress via status.json:
```bash
jq . status.json
```
Watch live:
```bash
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 log
- `stages/` — per-stage Claude output
- `context/` — 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`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!