Mark a logical phase completion in haivemind. More formal than /snapshot — used at step/phase boundaries in multi-phase work. Creates a named, resumable point that /continue can restore from. Triggered by /checkpoint, "checkpoint this", "mark this as a checkpoint", or at phase boundaries in long-running tasks.
Run the Qwen Code CLI as a one-shot bounded executor in a plan/do/verify loop. A frontier model (or you) plans the next bounded step and verifies the result; qwen-do makes a local model do exactly that one step, smoke-test first, then stop. Use when you want a cheap local model to do grunt coding while a smarter orchestrator keeps it on rails.
Scan git commits for PII, credentials, API keys, and passwords before they are pushed. Automatically gates commits via a pre-commit hook. Use when installing PII scanning on a repo, manually scanning a file or diff for credentials, or when a commit is blocked by the hook and remediation is needed. Triggers on "scan for PII", "check for credentials", "install PII guard", "pii hook", or when a commit is blocked by a PII check.
Runs a full CORE-EEAT 80-item content quality audit, scoring content across 8 dimensions with weighted scoring by content type. Produces a detailed report with per-item scores, dimension analysis, and a prioritized action plan.
Deep analysis and debugging with Opus. Systematically investigate problems, identify root causes, and recommend fixes with evidence.
PR review skill. Two modes: /pr [link] = internal thoughts only, what to look for, what to test — NO GitHub action ever. /pr-comment [link] "make it so #1" = draft a GitHub PR comment in <USER_NAME>s voice, present for approval, post only on explicit "go". Passphrase + "go" are both required before any GitHub write. Without both gates, nothing leaves the building.
Deep reflection and optimization with Opus. Two modes — /self-reflect analyzes completed work, extracts root causes, and stores lessons. /optimize analyzes a process or system, determines the right model and approach, then executes improvements. Use when reflecting on what happened, extracting lessons, optimizing workflows, or improving approaches. Triggers on "self-reflect", "reflect on", "optimize", "what went wrong", "what can we improve", "lessons learned".
Deep static analysis and bug hunting for any codebase.