Run a named codebase maintenance scan and convert findings into 6-component, agent-ready GitHub issues. Use when a workflow or user says "run the <name> scan", "create issues from this analysis", or passes a prompts/scans/*.md file. Handles dedupe, priority labeling, and max-issue caps so the Ralph loop never starves and never bloats. Do NOT use for implementing fixes (use stay-green), reviewing PRs (use comprehensive-pr-review), or closing/triaging existing issues (use backlog-grooming).
Audit the codebase for sloppy, amateurish, or AI-generated low-quality code — bugs, code smells, dead/stubbed/orphaned code, duplication, poor architecture, needless verbosity, comment slop, type-safety erosion, and weak tests — then file corroborated findings as Ralph-ready GitHub issues (and decomposed epics for big work). Use when the user says "de-slop", "deslopify", "run the slop detector", "find code smells", "audit code quality", "find dead code", "weekly code quality scan", "bullshit detector", or when the weekly de-slop GitHub Action runs. Findings must be corroborated by two independent signals before filing — null findings are a valid result. Do NOT use for implementing fixes (Ralph / continue-epic does that), for reviewing a specific PR diff (use comprehensive-pr-review), for fixing CI failures (use ci-debugging), or for triaging a backlog of existing issues (use backlog-grooming).
Configure per-stage LLM model routing for a Creek vault and perform the secure setup. Use when the user asks to "set up / configure my models", "/model-setup", "which model for classification / writing / frontend / the writing desk", "route classification local and writing to Sonnet", "wire up per-stage routing", or "pull the ollama models for creek". The skill detects the current `llm:` block, the environment (key presence + cloud consent), and Ollama reachability; writes the per-stage `llm:` block into the vault's 00-Creek-Meta/creek_config.yaml (config only); guides the user to set `ANTHROPIC_API_KEY` / `CREEK_CLOUD_CONSENT` in their environment; and offers to `ollama pull` the local models. It NEVER reads, echoes, logs, or writes an API key into any file. Do NOT use to edit routing source/tests (that is the per-stage routing code in `creek/classify/llm/`).
Launch the CrawDad Discord bot against a Creek vault. Use when the user asks to "launch CrawDad", "start the bot", "run CrawDad", "fire up the Discord bot", or otherwise bring the Discord-side interface online for a vault. ALWAYS ask which vault directory to run against first. Handles every launch gotcha (absolute vault_path, State/latest.md, voice-core mirroring, env secrets, allowlists) and starts the bot in the background. Do NOT use for driving the `creek` CLI / writing essays (use creek-cli) or editing crawdad/creek-tools source (use stay-green/work-issue).
Decompose a SPEC, PRD, RFC, or design doc into a sequenced set of GitHub epics and child issues, where each issue is a self-contained prompt an agent or engineer can execute end-to-end. Use when the user says "decompose this spec", "break this PRD into issues", "file epics from this design doc", or "plan the implementation". Each issue is shaped as a 6-component prompt (prompt-engineering), sequenced via tracer-code so the skeleton lands first and every later issue keeps the system demoable, and gated by stay-green Done-Done plus max-quality-no-shortcuts anti-bypass rules. Issue bodies are written to `git-issues/` and filed via `gh issue create --body-file`, matching the file-based pattern in git-workflow. Do NOT use for single-task issue or PR creation (use git-workflow), backlog cleanup of existing issues (use backlog-grooming), PR code review (use comprehensive-pr-review), or choosing between technical approaches inside a SPEC (use architectural-decisions).
End-to-end GitHub issue implementation: read issue, branch, TDD, quality checks, self-review, and PR creation. Use when given an issue number to implement, asked to "work on issue #N", "pick up #N", "implement #N", or "start issue #N". Orchestrates stay-green, max-quality-no-shortcuts, and self-review skills. Do NOT use for bug triage (use bug-squashing-methodology), backlog maintenance (use backlog-grooming), or reviewing others' PRs (use comprehensive-pr-review).
Iterate on Claude PR review feedback intelligently and merge when ready. Use when the user asks to "address feedback", "respond to Claude's review", "iterate on the PR", "fix review comments", or "merge if Claude said LGTM". The Claude reviewer publishes a top-level PR comment via GitHub Action ending in a `Verdict:` line (LGTM / CHANGES_REQUESTED / COMMENTS) — it is NOT a formal GitHub approval. This skill locates the most recent such comment via GitHub MCP, parses the verdict, triages blockers/problems/nits into a TDD-driven local fix loop, replies and resolves threads. On `LGTM` for the current HEAD with green CI it squash-merges; on `COMMENTS` it files each actionable item as a follow-up GitHub issue and then squash-merges; on `CHANGES_REQUESTED` it loops until LGTM. Do NOT use for giving a review (use comprehensive-pr-review), debugging CI failures themselves (use ci-debugging), general TDD work outside review context (use stay-green), bug RCA (use bug-squashing-methodology), or issue/branch/PR creation
Gentle, hand-held, end-to-end walkthrough of the Creek Vault + CrawDad system, voiced by CrawDad. Use when the user wants to be walked through using Creek — "walk me through", "how do I use this", "get me started", "show me the proper way", "I don't want to read the docs", or any request for guided onboarding. Claude runs every command FOR the user and narrates gently, one stage at a time, at the user's pace. The user only makes decisions and gives consent; they never read code, docs, or a README. Do NOT use for implementing FEATs (use work-issue), debugging CI (use ci-debugging), PR review (use comprehensive-pr-review), or when the user explicitly wants to read the docs themselves.