Review my code, code review, is this ready to ship, check for bugs, security audit, review this PR, pre-merge check, is this safe to deploy, check code quality. The specialist lanes and memory that the built-in /code-review doesn't have: it invokes the built-in engine for general bug-finding, then adds a mechanical hallucinated-imports validator (with a vendored slopsquat denylist; Python/JS/TS/Rust/Go), an AI-slop lane, framework IDOR heuristics, a Supabase/Firebase BaaS-RLS security lane, and a deterministic findings index that tracks CR-NNN IDs across runs (new / recurring / resolved). Fixes apply to the working tree only — never commits.
This skill should be used when the user says "adopt this repo", "bring this repo onto the doc model", "this repo predates the system", "onboard this existing project", "migrate this repo's docs", or when startup found an established repo without the doc model. Brownfield archaeology, read-only toward code: reads git history + docs + code, drafts AGENTS.md/handoff/decisions plus an architecture.md module map from evidence (verifying build/test commands by actually running them), triages every existing doc onto the shelf (keep / merge / satellite / archive — proposing each move, never silently deleting), asks only what evidence can't answer, stamps dormant repos, runs fit-out, and hands plan reconstruction to /rad-planner:rescue. Never changes code.
This skill should be used when the user says "repo-align", "align the repo", "clean up the repo", "check for drift", "is the repo in good shape", "find contradictions", "what's gotten messy", "doc cleanup", "are my docs consistent", "tidy up the docs", or when startup's trust report went red. The deep, opt-in alignment pass: mechanical scans (drift, freshness, structure drift, vocabulary, size budgets) plus judgment passes — a doc router that reads off-shelf files and proposes where their content belongs, a routes-vs-api.md and modules-vs-module-map diff, and an on-request rules audit of AGENTS.md. Proposes before acting on every judgment call; preserves history with git mv; never silently merges, deletes, or archives.
This skill should be used when the user says "set up this repo", "bootstrap this project", "new project setup", "scaffold the docs", "initialize the repo model", "get me started right", or when startup recommended it on a fresh repo. Builds the container for the doc model in a new or nearly empty repo: an AGENTS.md skeleton with the stamped doc-model block, the CLAUDE.md @AGENTS.md shim, docs/ + docs/archive/, and a handoff stub. Creates no shelf or initiative docs (their triggers haven't fired), runs no fit-out, never invents product content, and ends by recommending /rad-planner:plan. For an existing repo with history and docs, use /rad-repo-manager:adopt instead.
This skill should be used when the user says "ship", "ship it", "close out and push", "wrap and ship", "wrap it up and push", "send it", "close-out", "commit and push everything", or "end the session and push". The one-command close-out chain: align-lite → quick wrapup → reviewed staging → repository contract gate → conventional commit → push → deploy-verify (only when AGENTS.md declares a deploy: target) → stray branch/worktree sweep → one-line report. Invoking /ship IS the owner's authorization to commit and push — no re-asking. Target: under three minutes including deploy verification.
This skill should be used when the user says "startup", "start session", "orient me", "where did we leave off", "catch me up", "what's the state", "session briefing", or "what was I working on". Fast, read-only session orientation — read the L0/L1 docs + scoped instruction map + git state, run the cheap mechanical scans, and surface a trust report (one line per managed doc, measured in commits-behind) plus the next task from the handoff. Recommends /rad-repo-manager:repo-init on a fresh repo, /rad-repo-manager:adopt on an established un-managed repo, and /rad-repo-manager:repo-align when the trust report goes red. It does not scaffold, audit deeply, clean, write, or change anything.
This skill should be used when the user says "wrapup", "wrap up", "end of session", "save state", "handoff", "leave a clean stopping point", "I'm done for now", or "before I close". Quick by default (target under a minute): overwrites docs/handoff.md (≤60 lines) from git evidence — not chat memory — carrying the Deferred ledger forward, then asks exactly two questions: any decisions settled this session (append to docs/decisions.md)? anything blow up worth remembering (append to docs/lessons.md)? The deeper reconcile pass — checking whether the session left plan/prd/AGENTS.md stale, plus structural signals in the session diff (routes → api.md, modules/deps/migrations → architecture.md, visual decisions → design.md), drafting per-edit-confirmed fixes — runs only with --full (weekly use). No status/roadmap files, no auto-commit or push, never runs tests.
Delegate coding, debugging, analysis, or bulk mechanical work to the local OpenAI Codex CLI (GPT-5.5) running as a non-interactive sub-agent. Use when the user says "use codex", "ask codex", "have codex do/fix/build/implement", "get a second opinion from GPT/codex", when routing bulk mechanical work (migrations, spec implementations, data transforms) per standing routing rules, or whenever Claude Code needs to run the Codex CLI programmatically. For reviewing a diff/branch/commit, prefer the rad-codex:review skill.