systematic-debugging
Root-cause-first debugging workflow for software, exploit tooling, fuzzing harnesses, reverse-engineering helpers, C2/client code, flaky tests, crashes, races, and environment-specific failures. Use when a failure is not immediately obvious or when repeated quick fixes risk hiding the real defect.
v2026.11.13-21cd5683 instalações+3 em 7 dias39 EstrelasMITsincronizado há 10 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/systematic-debuggingGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacote7cdbcb9a…e2b50027
7cdbcb9a2008…9090e2b500274 arquivos · 5.9 KBVarreduraBaixo1 achado
- Links para domínios externos
Fontegithub.com/AeonDave/malskill/tree/main/coding-behaviours/systematic-debugging@21cd568
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
Diagnose software failures through observable state and controlled checks. Keep a suspected cause, an effective mitigation, and a verified fix distinct.
When to activate
- Crash, timeout, flaky test, exploit instability, silent corruption, race, or environment-specific failure.
- Repeated fixes have not explained or resolved the issue.
- The observed failure is far from the likely source: heap corruption, async timing, protocol state, ABI mismatch, or bad fixture isolation.
Workflow
- Frame and preserve: record expected versus observed behavior, affected scope, command/input, build, configuration, seed, and exact failure evidence as applicable. In an active incident, prioritize authorized containment or recovery; preserve useful evidence without delaying urgent mitigation. Follow Google SRE's triage guidance.
- Reproduce or compare: seek the smallest case retaining the same failure signal. If reproduction is unavailable or intermittent, compare failing and successful traces and relevant environmental differences; continue diagnosis with bounded claims. Do not reset state or discard the only failing artifact to get a clean run.
- Localize: classify the failure and inspect the actual execution path. Trace data, control, ownership, and configuration from the symptom toward the first violated contract; identify the next unknown boundary rather than assuming the crashing line is the cause.
- Test a prediction: state what the suspected mechanism predicts and choose a check that distinguishes it from plausible alternatives. Instrument that boundary with a log, breakpoint, sanitizer, packet/syscall trace, or watchpoint. Before reading a probe or forced change as evidence, confirm it actually took effect — the log line executed, the rebuilt artifact is the one running, the mutation differs from a pristine copy; a stale build, wrong binary, cached artifact, or edited-but-unused file turns a no-op into a false negative. Iterate tracing and experiments as results arrive; use
hypothesis-drivenwhen competing explanations need a structured investigation. - Correct the supported cause: make the smallest complete change that repairs the violated contract, including affected consumers. Keep a necessary workaround explicit when the underlying cause cannot yet be corrected. Preserve diagnostic evidence, then remove temporary probes or retain only useful, bounded diagnostics.
- Verify: add or update a regression test/reproducer where practical, check the original failure and relevant neighboring behavior, then run applicable broader checks. Use
testing-reliabilitywhen the test itself is suspect andverification-before-completionfor completion gates. For intermittent failures, report tested schedules, seeds, or workload and remaining uncertainty; a single successful run does not establish elimination.
When progress stalls
When patches or retries stop producing new evidence, stop speculative changes and reassess the observation, environment, and causal model. Use loop-control-and-pivots; a fixed attempt count does not diagnose the defect. Continue useful investigation within the authorized scope.
Offensive debugging focus
- Exploit dev: verify offsets, mitigations, architecture, target build, and debugger side effects.
- Fuzzing: preserve the original input, minimize while retaining the failure signature, and record seed/corpus and instrumentation. Check whether replay outside the fuzzer reproduces the same defect; record environment differences when it does not.
- Shellcode/BOF/loader work: check ABI, stack alignment, calling convention, clobbered registers, and import resolution.
- Network tooling: capture wire data before changing parser or retry logic.
- Evasion research: distinguish bypass failure from environmental control, policy, or telemetry differences.
Resources
Load only the reference matching the unresolved step:
- references/root-cause-tracing.md — load for downstream symptoms, regression isolation, or tracing state across boundaries.
- references/condition-based-waiting.md — load for startup, async completion, or timing failures where a wait observes the wrong condition.
- references/defense-in-depth.md — load after diagnosis when deciding whether a boundary guard or another prevention layer adds value.
Use software-guidelines for scoped repository edits and software-architecture when the correction changes boundaries or ownership. Report the failure, supported causal chain or remaining hypothesis, delivered change, checks, and limits; use evidence-before-claims when the strength of a causal claim is uncertain.
Arquivos desta versão
references/38.2 KB
- condition-based-waiting.md3.1 KB
- defense-in-depth.md1.1 KB
- root-cause-tracing.md4.0 KB
- SKILL.md5.3 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Não | Não |
| Roda comandos no shell | Não | Não |
| Usa a rede | Sim | Sim |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- InfoLink · Links para domínios externos
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 de nov. de 2026 | 21cd568 | 7cdbcb9a | Assinada | – |
Mais de AeonDave
Tudo deste publicadorMais em Engenharia reversa e fuzzing
Ver a categoriaPergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login