agent-smith

Start an Agent Smith ticket the right way — read the ticket, its dependencies, the PRD Decision Log, and the affected architecture/docs before editing. Use when picking up an AS-NNN ticket, deciding what to work on next, or before touching code for a backlog item. Triggers: "work on AS-", "start a ticket", "implement the ticket", "what should I work on next", "pick a ticket".

Agent Smith pull-request lifecycle — open a PR, subscribe to activity, reply to and resolve every review thread, handle the Gemini/Copilot review order, and auto-merge when clean. Use when work on a branch is committed and pushed, when a PR exists for the branch, or when handling review comments or CI on a PR. Triggers: "open a PR", "PR review", "review comment", "CI failed on the PR", "merge the PR", "is the PR ready".

Reflect phase — produce the three success artifacts (a measurable success metric, an instrumentation diff, a check-back ticket draft) without ever reading shipped-app runtime data.

Analyse phase — trace what else the change touches: callers, shared state, persisted formats, and cross-package contracts.

Analyse phase — interrogate the request for missing requirements, unstated assumptions, and unhandled cases before any code is written.

Plan phase — pressure-test the proposed plan: smallest viable change, ordering, and the test that will prove it.

Reflect phase — capture what was learned as durable, grounded notes: surprises, follow-on tickets, and method tweaks.

Verify phase — confirm the change actually works: tests run, gate passes, acceptance criteria met, claims grounded in output.

Map a failing Agent Smith CI job to the local harness command that reproduces it and produce the shortest reproduction plan. Use when a GitHub Actions check is red, a PR's CI failed, or someone asks why CI broke and how to fix it locally. Triggers: "CI failed", "check is red", "reproduce the CI failure", "why did the build break", "make CI green".

Choose, run, and interpret the Agent Smith harness quality gates when finishing or handing off code changes. Use when you have edited Go code and need to validate it, when deciding between the quick/full/arch checks, when a gate fails and you must classify the failure, or when a command can't run in the current environment. Triggers: "run the gate", "quality gate", "before commit", "is this ready to push", "harness check", "make test/vet/lint".

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Drops articles, filler, hedging, pleasantries. Preserves all code, technical terms, error strings verbatim. Supports intensity levels: lite, full (default), ultra, wenyan variants. Use when user says "caveman", "caveman mode", "talk like caveman", "less tokens", or invokes /caveman.