Audit pipeline: LEGACY SPELLING of /audit:layout sharded — it still works and does exactly that. Kept so existing transcripts, runbooks and older docs resolve; new work should say /audit:layout , which also goes back the other way.
Audit pipeline: open / stop / check a local control-panel UI to visually manage .claude/audit.config.json and the manifest's composition levers (reviewSkill, per-task skills/models, buildCommands) — with live validation and discovery of the skills & agents available in this repo + globally. Ephemeral, on-demand; a…
Audit pipeline: everything a phase has done to it — add one to a plan that already exists, run it end to end (every ready task, parallel where safe, then sign-off), pin which phase the pipeline reaches for first, or cancel one that will not be done. A bare runs it; --dry-run previews the run without mutating.
Manage parked phase proposals in the audit manifest — list them, materialize one (or all) into live phases, or drop one. Proposals are parked by /audit:init when the user declines (some of) the synthesized plan; materialization is a move, not a re-synthesis.
Audit pipeline: render a self-contained, interactive HTML + Markdown report (collapsible phases, filter/sort, optional AI summary, Save-as-PDF) — shareable as a CI artifact, or published to a link with --share. Read-only (never mutates the manifest).
Audit pipeline: print manifest status — phases, tasks, bugs, the ready-now list and what each pending task is waiting on; or, with --gate, turn that same state into a CI pass/fail verdict over conditions you pick with --fail-on. Read-only, no locks, no mutations.
Sync the audit manifest with Azure DevOps work items — set the connector up for the first time (connect: verify the transport, report which auth path is in effect, prove access read-only, detect the board's process), push manifest bugs/tasks/phases to ADO (board states, sprint stamp, Remaining Work, comments), pull…
Add a tracked task to the audit manifest — every answer is a flag, and the dialogue only covers what the caller did not pass — move one between phases, or cancel work that will not be done. add allocates the id, initializes all orchestrator fields, updates fileIndex, and revalidates; move renumbers a task into another…
Audit pipeline: token spend attributed by phase, task, model, author and time — with cache economics, cost-per-task and a usage trend. Read-only (never mutates the manifest).
Audit pipeline: create (or remove) a git worktree for a phase so you can run it in a parallel session. Claude does the git worktree add + derives the phase branch; you just open a Claude session in the printed path and run /audit:phase there. Sharded manifests merge back conflict-free.
Runs before the agent uses a tool for Read, Grep, Bash, Bash, Skill, Task, Agent, mcp__.*, Edit, Write, MultiEdit and NotebookEdit tool calls, executing py-launch.sh via sh (6 commands). From AleksandarBisevac/claude-plugins.
Runs after a tool call finishes for Edit, Write, MultiEdit, NotebookEdit and Bash tool calls, executing py-launch.sh via sh (6 commands). From AleksandarBisevac/claude-plugins.
Use when someone wants a whole codebase audited and fixed as tracked, resumable work — "audit this codebase", "find and fix everything wrong in this repo", "go through the app and clean it up", "set up an audit plan", "what audit phase is next" — rather than a one-shot look at the current diff. Routes to the /audit…
Use when someone asks what their Claude Code work has cost — "what did that cost", "how much have we spent", "where did the tokens go", "which model is burning the budget", "is the cache actually helping" — and wants it attributed to the work rather than a session total. Routes to /audit:usage.