crew-afklisted

Implements all ready-for-agent issues in the current repo by dispatching each one to a crew-coder subagent (a separate pi process in an isolated git worktree), then housekeeping the result. Loops until no issues remain or all are stalled. Reviews every branch before it merges. Use when asked to run an AFK sprint or implement all open issues. Optional: --model <alias|inherit> to override the coder's default model; --coverage for a PRD coverage report; --promote critical-high to promote HIGH review findings as well as CRITICAL.
ypxing/coding-crew · ★ 1 · AI & Automation · score 64

Install: claude install-skill ypxing/coding-crew

# AFK Issue Sprint — pi The sprint is a program, not a prompt. You launch it, stream its output, and report what it printed. **You do not orchestrate, implement, review, merge or close anything yourself.** ```bash CREW_AFK="$(git rev-parse --show-toplevel)/.coding-crew/crew-afk/main.mjs" [ -f "$CREW_AFK" ] || CREW_AFK="$HOME/.coding-crew/crew-afk/main.mjs" node "$CREW_AFK" run --platform pi "$@" ``` Pass the user's arguments straight through: `--model <alias|inherit>`, `--coverage`, `--promote critical-high`, `--max-parallel N`, `--worker-timeout <minutes>`, `--max-rounds N`, `--no-squash`, `--jira TICKET-123`, or a `.scratch/<feature-slug>/…` path. Unrecognised arguments are forwarded to session setup, so never rewrite them. It owns the whole loop: session init, issue selection, a worktree and a `crew-coder` process per ready issue, then per branch `verify → review (acceptance criteria + findings) → merge → close`, then findings promotion, squash, cleanup and the summary. It loops until no issues remain or two rounds complete nothing. ## Your part 1. Run the command above, with `--dry-run` first **only** if the user asked what it would do. 2. Stream stdout as it arrives. The summary it prints is the report — do not rewrite, summarise, or re-derive it from the state file. 3. Report the exit code's meaning and stop: `0` finished, `2` stalled (blockers need a human), `3` no ready issues, `1` setup problem — print its stderr verbatim and stop. ## Failure handling -