← All creators

willprout

User

Worth it for exactly the three qu

4 indexed · 0 Featured · 1 stars · avg score 55

Categories

Indexed Skills (4)

Code & Development Listed

cross-review

Get an independent second-opinion review of a file (plan, spec, code change, anything) from a different model family via the Codex CLI — or, on a Claude-only machine, from a fresh same-model subagent that wrote none of the code. Use when finishing a high-stakes artifact (plans, designs, refactors) or to satisfy the loop's fresh-agent review duty before a final commit; not for trivial edits. Invoked as /superlooper:cross-review <file> [focus hint].

1 Updated 5 days ago
willprout
Code & Development Listed

sl-debugger

Live diagnosis and repair of a broken superlooper + command-center instance on this machine. Use when the loop or dashboard misbehaves — a wedged tick, a storm of parks or notify texts, a stuck label, a frozen or silent queue, a runner that looks alive but does nothing, a dashboard painting everything dead — or when asked for a health check of a running loop. Routes to a read-only health readout, documented failure classes with repairs, a safest-first repair ladder, and the unattended-invocation contract for the mechanical watchdog.

1 Updated 5 days ago
willprout
AI & Automation Listed

superlooper

The universal issue-loop workflow. Use when writing or approving loop issues, adopting a repo into the loop, running or operating the loop runner, reading the morning report, or preparing a dev→prod promotion. Agents write GitHub issues that William approves by his word (recorded as a label); a deterministic runner builds one fresh Claude session per approved issue in its own worktree; a mechanical per-PR gate merges to the dev mainline; promotion is William's batched judgment. Routes the issue-writing job to the write-issue skill and adoption to the adopt skill; carries approval and ops as its own references.

1 Updated 5 days ago
willprout
AI & Automation Listed

write-issue

Use when drafting or filing a GitHub issue for the superlooper loop — the rigorous body format (Goal / Definition of done / Boundaries / Loop metadata), the thin-issue "point, never assert" doctrine, the one `type:` label, `touches:`/`blocked-by`/`parent`, turning cross-PR promises into issues, and filing with `gh` carrying every label except `agent-ready`. Agents draft loop issues; William approves them by his word.

1 Updated 5 days ago
willprout

Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.