validate-db
Validate Prisma schema against requirements specification (read-only)
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Validate Prisma schema against requirements specification (read-only)
Validate Controllers and DTOs against requirements (read-only)
Validate Providers against interfaces (read-only)
Registrador de bugs do Reversa. Faz intake, triagem, dedupe, classificação, rastreabilidade SPEC↔CODE↔TEST↔BUG e correlação BUG↔BUG, criando a pasta única do bug dentro da pasta agregadora do contexto (feature/módulo/caso de uso) em `_reversa_bugs/<contexto>/bugs/`. Nunca corrige. Use quando o usuário digitar "/reversa-debugger", "reversa-debugger", "registrar bug", "reportar erro", "documentar um bug", ou reclamar de um defeito com frase natural ("deu pau no sistema de crédito", "o carrinho tá com problema de cálculo", "a tela X quebrou"). Ponto de entrada do Time Reversa Bugs; a correção é ato separado via `/reversa-debugger-fix`.
Corretor de bugs do Reversa, orquestrador do ciclo de vida do defeito. Reproduz, investiga causa raiz com evidências, oferece debate multiagente opt-in, cria testes de reprodução e regressão, aplica o Correction Change Set com diffs aprovados em dois gates, dá o veredito de spec (com adendo versionado quando a spec muda) e fecha conforme a closure policy. Use quando o usuário digitar "/reversa-debugger-fix", "reversa-debugger-fix", "corrigir o bug", "consertar o BUG-XXX" ou pedir a correção de um bug registrado. Exige bug registrado via `/reversa-debugger`.
Reviews code, docs, examples, and agent-produced changes that use Reatom. Use when reviewing Reatom pull requests, examples, migrations, model files, async flows, routing, forms, persistence, or documentation that claims Reatom behavior.
Use this when the user wants a draft paper, figure bundle, README, release page, or experiment artifact reviewed before sharing. Checks evidence binding, claim scope, captions, layout clarity, and release readiness.
Use this when the project needs a dedicated data-quality review before model review. Checks data reality, split correctness, label health, leakage risk, shape consistency, and mock-data disclosure.
Verify that Minutes is properly set up and working — model downloaded, mic accessible, directories exist, no stale state. Use when the user says "is minutes working", "check my setup", "verify minutes", "test recording setup", "why isn't minutes working", "minutes health check", or after running setup for the first time.
Diagnose a problem with a Happier session, the daemon, a provider (Claude/Codex/OpenCode), auth, or connectivity. Pulls the correct logs, finds a true root cause from evidence only, presents findings, and optionally uploads a private diagnostics bundle to Happier developers and/or files a sanitized public GitHub issue (the two are complementary). Use when the user reports a bug, says Happier is broken/stuck/misbehaving, asks to debug/diagnose/triage/troubleshoot Happier, or shares a Happier session ID and asks what went wrong.