Menu
Metodologia científica de debugging. Usar quando: "debug", "bug", "erro", "não funciona", "investigar problema", "por que isso quebrou".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Visualize an agent's perceive→think→act loop. Inspects tool calls, latency per step, decision branches, retry patterns. Surfaces bottlenecks. Triggers on "trace agent", "why is agent slow", "agent loop analysis", "what did the agent do".
Compute context window budget for a prompt/agent — sums system prompt, tool descriptions, examples, conversation history; flags overruns; suggests cuts. Triggers on "context budget", "how much context", "will this fit", "budget my prompt".
Treat dataset / eval JSONL as code — lint, validate schema, detect duplicates, leakage between train/eval, label imbalance, PII. Karpathy "Software 2.0" lens. Triggers on "audit dataset", "lint jsonl", "check for leakage", "validate eval data".
Enforce "evals over vibes" — before any prompt, agent, or model change, require an eval set with success criteria and baseline measurement. Blocks vibe-only changes. Triggers on "tune prompt", "improve agent", "change model" without prior eval set.
Build a 10-30 case eval dataset from a PRD, skill, or prompt — covering golden path, edge cases, and adversarial inputs. Output as JSONL with input/expected/category. Triggers on "build eval set", "create evals", "generate test cases for prompt".
Break down any ML/AI concept to first principles — strip jargon, derive from basics, build physical/mathematical analogy. Karpathy intuition-building style. Triggers on "first principles", "explain like I'm 5", "derive from scratch", "why does X actually work".
| name | debug-workflow |
| description | Metodologia científica de debugging. Usar quando: "debug", "bug", "erro", "não funciona", "investigar problema", "por que isso quebrou". |
Nunca pule etapas. Cada etapa deve ser confirmada antes da próxima.
Crie o menor caso reproduzível possível.
Identifique a menor unidade de código responsável.
git bisect para encontrar o commit que introduziu o bugForme UMA hipótese sobre a causa raiz. Seja específico:
Execute o MENOR experimento para validar/refutar:
# Adicionar log temporário
console.log('[DEBUG]', { variavel: x, estado: y });
# ou usar debugger
node --inspect-brk script.js
Aplique o fix MÍNIMO que resolve a causa raiz. Evite "enquanto estou aqui" refactoring.
npm test)# Encontrar commit que introduziu bug
git bisect start
git bisect bad HEAD
git bisect good <commit-hash-bom>
# git bisect good/bad até encontrar o commit
# Ver histórico de uma linha específica
git log -L 42,42:src/arquivo.ts
# Stash para isolar mudanças locais
git stash && npm test && git stash pop