Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Dual-mode implementation agent. The orchestrator declares the mode in the dispatch prompt. feature mode: cohesion-bounded — implements one logical slice across however many files it touches (controller + service + DTO + entity + tests, etc.); refuses cross-cutting or ambiguous scope. surgical mode: hard cap of 2 files…
Read-only code locator. Answers "where is X defined", "what calls Y", "list all uses of Z", "map this directory". Returns file:line table, no prose. Refuses to suggest fixes or speculate about design. Use to save main-context tokens on exploration.
Diff / branch / file reviewer with two modes. Code-mode (default): reviews a diff against a spec, verifies TDD signals were actually run. Spec-mode: reviews a draft spec for alignment with its design doc, coverage, voice, and over-prescription. One line per finding, severity-tagged, no praise, no scope creep. Output…
Heavyweight reasoning agent. Runs at high effort on the caller's model. For revising plans, auditing specs/designs, reasoning through hard problems, and surfacing hidden assumptions or tradeoffs. Read-only. Does not implement, does not gate diffs, does not locate code. Use when the question is "is this the right…
Writes one wiki page from source. Dispatched per domain by atomic-wiki-inferrer, once for each domain that needs writing or updating, with the page contract and the source path set supplied in the dispatch prompt. Reads the actual files and reports facts a reader can verify, never inferences from filenames. Carries…
Route a lost user to the right atomic verb, skill, agent, or binary subcommand. Bare invocation reads git state and recommends one next step. Topic keyword or freeform intent → focused pointer. tour → guided walkthrough of the system. Help router, not duplicated docs.
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.
Autonomous delivery: plan, run the implement→review loop, ship. Takes a task or a GitHub issue number and an optional merge verb. Asks one question, how to merge, and only when the verb was not given.
Multi-lens design challenger. Reads a design/spec/plan/proposal, profiles it (who can reach it, whose data, what being wrong costs), then seats 3-6 expert lenses from a 30-lens catalog spanning engineering, data/ML, business, finance, communication, and delivery — each seated only with a cited stake, reflexive picks…
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
Bootstrap and maintain project documentation surfaces. Two modes: bootstrap (discover doc files, index them in CLAUDE.md) and authoring (scan for unindexed docs, match diff against indexed surfaces, walk stale/incomplete/missing items with Yes/Later/Remind/Skip).
Review and act on pending reminders. Bare invocation shows all reminders as an indexed list; cron-fired invocation (/follow-up due ) surfaces the specific reminder and waits for a response; /follow-up review lists stale project follow-up entries for per-item disposition (extend/close/promote/skip). Transport-aware…
Pre-design evidence gathering. Takes a hunch or hypothesis and chases it through primary sources (context7, official docs, source code, ast-grep, run-it experiments) before any spec is written. Returns SUPPORTED / UNSUPPORTED / MIXED / INCONCLUSIVE with cited evidence trail. Pairs with /pressure-test and precedes…
Scan and clean up stale git state — worktrees, local branches, optionally remote tracking refs. Dispatches a read-only scan via atomic prompt git-cleanup, presents an indexed report, asks user which to clean. No destructive ops without explicit confirmation. Defaults: 30-day staleness, local-only.
Socratic challenger for design decisions. Pressure-tests assumptions, surfaces contradictions, forces fuzzy maybes into yes/no — through questions only, never producing code or artifacts. Pairs with /atomic-plan as a pre-approval gate.
Implement→review subagent loop with no planning phase, for a fix whose cause is known and whose shape is obvious, however many files it touches. No spec, no worktree, no docs or signals at the end; one audit. Routes to /subagent-diagnose on an unknown cause and to /atomic-plan on an open approach or contract choice.
Refresh the project wiki. Handles both repo scope (docs/wiki/ inside the current repo) and realm scope (a cross-repo wiki at /wiki/). Scope auto-detected from block or directory structure. Dispatches atomic-wiki-inferrer, which reads the matching pipeline reference and executes it.
Session retrospective. Mines session history extracted by atomic retro extract and this conversation for friction, corrections, and misbehavior; cross-references installed artifacts; walks findings one at a time. Persists a run log so later runs detect drift. Use after long sessions or repeated friction.
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
★not rated 112▲
+5 8d agoA31 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: