Deep-dive performance audit of database queries, algorithmic complexity, frontend bottlenecks, and resource leaks for a PR, a commit, or the whole codebase, producing a severity-ranked report. Use when the user explicitly wants a dedicated performance review, asks to "audit performance", "find N+1 queries", "check for…
Adversarially review an implementation plan before any code is written, checking it against the actual repository rather than reading it on its own terms. Trigger on "review this plan", "poke holes in this plan", "what's wrong with this approach", or an automated pre-build gate. Assumes the plan is wrong and reports…
Perform an OWASP Top 10-focused static security review of a PR, commit, or entire codebase, grep for vulnerable patterns (injection, broken access control, crypto failures, hardcoded secrets), verify each match by reading it in context, and produce a severity-ranked report with file:line evidence and fix suggestions.…
Orchestrates the current branch from "code done" to "merged": runs the review-code skill, then any project-specific pre-merge checks it detects (visual regression like just visual-diff, tests, lint), then a conventional commit per git-commit, a PR per git-create-pr, and optionally watches CI and merges on green. Use…
Spec-driven team orchestration for large, multi-component features or new epics: writes a full spec/design/review artifact trail under .specs/, gates code changes behind an explicit user approval, then scales a team from 3 (lite) to roughly 9 (full) agents based on complexity. Use for sizable features spanning…
Multi-agent review team: architecture, security, performance, testing, style, docs/UX, plus an adversary that cross-examines the other 6, for security-sensitive, architectural, or large PRs (15+ files) where a single-agent pass risks missing cross-cutting issues. Use for auth/payments/PII changes, schema/pattern…
Generates a test suite by analyzing coverage gaps, prioritizing critical and untested code paths, then writing tests in parallel that match the project's existing patterns. Use when the user wants to write tests, add test coverage, generate test cases, improve testing, or analyze coverage gaps. Supports pytest…
Runs the project's visual regression testing (VRT) workflow, detects whatever tooling the repo actually uses (justfile/Makefile/package.json targets like visual-diff or visual-update, Storybook test-runner, Playwright screenshot tests, Chromatic, Loki, Percy), executes the diff, and triages every failure as a real…
Re-explain your own previous message in plain, simplified English (ASD-STE100 style), when the user did not understand it. Use when the user replies with "wtf", "what?", "I don't get it", "explain that again simpler", "ELI5", or "in plain English". Rewrites what was already said; it does not do new work, new research…