Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/systematic-debuggingReverse engineering e fuzzing

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 installazioni+3 in 7 giorni39 StelleMITsincronizzato 11 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/systematic-debugging

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
Ne8k0KV1Ok…LnnWuuCA==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto7cdbcb9a…e2b50027
7cdbcb9a2008…9090e2b500274 file · ⁦5.9 KB⁩
ScansioneBasso1 segnalazione
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/AeonDave/malskill/tree/main/coding-behaviours/systematic-debugging@21cd568

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

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

  1. 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.
  2. 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.
  3. 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.
  4. 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-driven when competing explanations need a structured investigation.
  5. 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.
  6. 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-reliability when the test itself is suspect and verification-before-completion for 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.

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellNoNo
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.11.13-21cd56813 nov 202621cd5687cdbcb9aFirmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login