← ClaudeAtlas

staged-coding-0-chaselisted

staged-coding stage 0 - chase what's already open (and stage 0.5 - pick a ticket if none was handed to you). Re-checks every PR this pipeline opened previously, resolves the run's ledger path, and when self-selecting enforces strict severity order. Signs its ledger line on finish. Triggers: /staged-coding-0-chase, or invoked in order by /staged-coding.
Shadysmetools/claude-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill Shadysmetools/claude-skills
# Stage 0 - chase what's already open (+ Stage 0.5 - pick a ticket) Part of the `/staged-coding` chain. Runs FIRST, every run, before Stage 1 (recon). Callable alone (e.g. to re-check a prior run's open PRs without starting a new ticket), but the conductor `/staged-coding` is the normal door and carries the cross-cutting rules (unit of work = the whole epic, lane = bug vs epic, which model builds vs checks, the ledger law, stop conditions). Read those there; do not duplicate them here. ## Inputs - `.staged-coding.json` in the repo root (see the conductor's `config.example.json`) - `state/pipeline-prs.json` (or your own equivalent): the list of PRs this pipeline opened previously - Whether the project owner or a dispatching agent already named a specific ticket (decides whether Stage 0.5 runs at all) - Read/write access to `config.boards.bugs` and `config.boards.product` - `config.home_checkout` on `config.base_branch` and clean. It is the read-only home base: never branch or commit inside it. ## What to do ### Resolve the ledger path (once, for the whole run) The ledger is `<worktree>/.staged-ledger-<ticket>.jsonl` (add it to `.git/info/exclude`). Resolve it here and pass the SAME path as `--ledger` on every sign call for the rest of the run, including calls made by checkpoint subagents. A subagent has its own working directory; letting it pick a path silently forks the ledger and makes `check` report stages missing that genuinely ran. ### Stage 0 - chase what's al