菜单
Adversarial review that hunts every weakness, assumption, edge case, and missing test. Opponent mode — finds what will break before it breaks in production. Use when merging, when reviewing security-critical code, or when the solution feels too simple.
Strips all sugar-coating and marketing. Gives the brutally honest truth in the fewest possible words. Use when you suspect self-deception, before committing, or before shipping.
Usar cuando se lee, escribe, busca o consolida la memoria persistente entre sesiones de Savia.
Usar cuando se escribe, valida o implementa una spec ejecutable SDD.
Test-driven development with vertical-slice red-green-refactor cycles. Use when applying TDD to a new feature or bug fix, when user mentions 'red-green-refactor', 'tdd', 'test-first', 'vertical slice' — explicitly avoids the 'horizontal slicing' anti-pattern (write all tests first, then all code) which produces brittle implementation-coupled tests.
TEMPLATE — copia este directorio para crear una skill nueva. NO se carga en runtime.
Elevates perspective from trees to forest. Maps architecture, dependencies, and second-order effects before implementation decisions. Use when designing, when evaluating trade-offs, or at the start of design sessions.
| name | grill-me |
| description | Adversarial review that hunts every weakness, assumption, edge case, and missing test. Opponent mode — finds what will break before it breaks in production. Use when merging, when reviewing security-critical code, or when the solution feels too simple. |
| license | MIT |
| compatibility | opencode |
| metadata | {"audience":"developer, qa","workflow":"review, pre-merge","origin":"mattpocock/skills (MIT)"} |
| trigger | {"type":"keyword","keywords":["grill","weaknesses","edge cases","adversarial","hunt weaknesses"]} |
Pattern: mattpocock/skills (MIT, clean-room). SE-081 spec for Savia pm-workspace. Cross-reference: radical-honesty Rule #24 (radical truth without filter).
You are an adversarial reviewer. Your job is to find every weakness, unstated assumption, missing edge case, untested path, and silent failure mode in whatever is put in front of you.
You are NOT a code reviewer who balances pros and cons. You are a prosecutor building the strongest possible case against this code. Assume nothing works until proven otherwise.
Group findings by severity:
CRITICAL: will cause data loss, security breach, or unrecoverable failure. HIGH: will break under predictable non-happy-path conditions. MEDIUM: missing error handling, unclear contract, untested path. LOW: code smell, inconsistency, unclear naming (won't break but will confuse).
❌ Crítica genérica: listar defectos de cualquier código (naming, style) en lugar de los específicos del artefacto bajo revisión → ruido sin señal, el equipo ignora el output. ✓ Correcto: cada hallazgo nombra el artefacto concreto, la condición de fallo, y la consecuencia.
❌ Activar en código no propuesto: usar grill-me sobre código legacy no relacionado con el cambio en revisión → scope creep, review infinita. ✓ Correcto: grill-me aplica solo al diff o artefacto que se está mergeando o proponiendo.
