implement-issue
Use when given a GitHub issue number and base branch to implement end-to-end
69
55%
Does it follow best practices?
Impact
93%
3.20xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/implement-issue/SKILL.mdEvaluation results
100%
80%Issue Implementation Runbook
Correct orchestrator invocation and monitoring
Start announcement format
0%
100%
Correct script path
0%
100%
Correct --issue flag
100%
100%
Correct --branch flag
100%
100%
One-shot status check
0%
100%
Live watch command fields
0%
100%
Watch interval
0%
100%
Log directory path
0%
100%
Log subdirectories
0%
100%
quality_iterations field
0%
100%
100%
78%Multi-Issue Dispatch Script
Specialist agent selection by issue type
CI workflow agent
0%
100%
Minified JS agent
0%
100%
Electron Linux agent
0%
100%
Packaging agent
0%
100%
Bash scripting agent
0%
100%
--agent flag syntax
100%
100%
Correct script path
0%
100%
--branch flag present
0%
100%
Correct --issue flag per call
0%
100%
Routing rationale documented
100%
100%
80%
34%Resilient Issue Implementation Wrapper
Exit code handling and pipeline stage awareness
Exit 0 meaning
62%
100%
Exit 1 meaning
62%
100%
Exit 2 meaning
90%
100%
Exit 3 meaning
90%
100%
All four codes handled
100%
100%
Correct script path
0%
100%
Correct issue and branch
100%
100%
Pipeline stage enumeration
0%
100%
Stage order correct
0%
100%
Schemas location mentioned
0%
0%
Integration context
0%
0%
- Repository
- aaddrick/claude-desktop-debian
- Commit
814cd52
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.