Roda code review via Claude Code CLI (Anthropic) com Opus 4.7 na branch atual, processa o output e classifica achados em P1/P2/P3 por categoria (lógica, sintaxe, estilo, segurança). Ativar quando Felipe disser "/claude-review", "roda claude review", "review com claude", "review com opus", "pede pro opus revisar"…
Roda code review via OpenAI Codex CLI na branch atual, processa o output e classifica achados em P1/P2/P3 por categoria (logica, sintaxe, estilo, seguranca). Ativar quando Felipe disser "/codex-review", "roda codex review", "review com codex", "pede pro codex revisar", "codex review nos ultimos commits".
Framework estruturado de debugging baseado nos 4 pilares de Pólya (How to Solve It). Ativar quando Felipe disser "/debug-polya", "debugar isso", "por que tá quebrando", "investiga esse bug", "o que tá causando isso", "não tá funcionando", "analisa esse erro". Força o agente a pensar metodicamente antes de sair mexendo…
Roda code review via Gemini CLI (Google) na branch atual, processa o output e classifica achados em P1/P2/P3 por categoria (lógica, sintaxe, estilo, segurança). Ativar quando Felipe disser "/gemini-review", "roda gemini review", "review com gemini", "pede pro gemini revisar", "gemini review nos últimos commits".
Ultra-compressed communication mode. Cuts token usage 75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
Build a throwaway prototype to flush out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine…
Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
Registra incidente ou aprendizado técnico no hub centralizado + cópia local no projeto. Ativar quando Felipe disser "/registrar-incidente", "registra incidente", "documenta esse problema", "registra aprendizado", "isso virou incidente", "guarda esse erro pra não repetir", "cria registro do bug", "registra o que deu…
Strict read-only verification workflow for claimed code fixes in any repository. Use when a user provides changed files or commits and asks to confirm each fix is structurally correct, reachable at runtime, and regression-safe, with required command execution and a report file containing per-fix PASS/FAIL/WARN…
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
★not rated 2 1mo agoA32 tokens
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: