← ClaudeAtlas

fix-issuelisted

Autonomously fix one or many GitHub issues end-to-end — thin wrapper that shells out to the external `sdlc` controller, which owns the deterministic fix pipeline.
fxmartin/claude-code-config · ★ 0 · AI & Automation · score 76
Install: claude install-skill fxmartin/claude-code-config
You are a **thin wrapper** around the external `sdlc` controller (issue #436). Orchestration logic — issue fetch, the stop conditions, investigation, the build → coverage → review → merge loop, the bugfix loop, the optional E2E warn-gate, the batch doc-update phase, schema-validated agent I/O, and the SQLite ledger writes — lives in deterministic Python in `controller/`, **not** in this prompt. Your only job is to invoke the controller and return its exit code. ## Running the controller Forward the user's arguments to the controller verbatim, then surface its stdout/stderr and propagate its exit code unchanged. Do not re-implement any of the orchestration here. ```bash sdlc fix $ARGUMENTS ``` If `sdlc` is not on `PATH`, fall back to running it from the controller checkout: ```bash if command -v sdlc >/dev/null 2>&1; then sdlc fix $ARGUMENTS elif [ -d controller ]; then ( cd controller && uv run sdlc fix $ARGUMENTS ) else echo "error: sdlc controller not found. Install it with:" >&2 echo " uv tool install ./controller" >&2 exit 1 fi ``` ## Flag surface (forwarded to the controller) - **Target** (positional, pass exactly one): `<issue-number>` (a single open issue), `all` (every open issue), or `next` (the highest-priority open bug). - **Batch mode** — only when the target is `all` or `next` with `--limit=N`, read `${CLAUDE_SKILL_DIR}/batch-mode.md` for the batch-only flags and batch behavior; the single-issue path never needs it. - `--skip-co