Skip to content
Skills Library
Programming · Analysis

evidence-driven-debugging

/evidence-driven-debugging

Investigate and fix defects by reproducing the reported path, comparing hypotheses, and checking runtime behavior. Use for bugs, regressions, intermittent failures, and fixes needing evidence beyond a plausible code change.

Licence
MIT
Last repository change
31.10.2026

Assessment and security

85/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content20 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 31.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Investigate and fix defects by reproducing the reported path, comparing hypotheses, and checking runtime behavior. Use for bugs, regressions, intermittent failures, and fixes needing evidence beyond a plausible code change.

Original author description

Investigate and fix defects by reproducing the reported path, comparing hypotheses, and checking runtime behavior. Use for bugs, regressions, intermittent failures, and fixes needing evidence beyond a plausible code change.

How it works

  1. Find a decisive observation
  2. Make the check useful
  3. Fix and verify
Original SKILL.md headings · 27 lines, 244 words
SKILL.md preview
---
name: evidence-driven-debugging
description: Investigate and fix defects by reproducing the reported path, comparing hypotheses, and checking runtime behavior. Use for bugs, regressions, intermittent failures, and fixes needing evidence beyond a plausible code change.
---

# Evidence-driven debugging

Follow the exact path the user reported. A passing check on a nearby subsystem does not explain the defect.

## Find a decisive observation

Record the symptom, expected behavior, revision, inputs, and environment. Trace the action through the real UI, API, persisted state, or artifact pipeline.

Reproduce the failure or identify the smallest observation separating the leading explanations. Include a competing explanation for an obvious first guess when evidence is ambiguous.

A page can display stale data while the query is correct. An asset can exist while production imports an older hash. A count can measure events while the user asked about distinct participants.

## Make the check useful

Choose the smallest check exercising the failing behavior. If adding a regression gate, show that it detects the broken state before fixing it. A deliberate negative control can reveal whether the gate reads runtime behavior.

A screenshot, network response, or raw measurement can be decisive. Use the form appropriate to the symptom. Do not replace a visible failure with a claim based only on syntax or a build.

## Fix and verify

Change the cause within scope. Rerun the failure case and nearby affected contracts. Preserve unrelated work, ownership boundaries, and accepted product decisions.

Record the cause, changed behavior, verification command or capture, and material limits in the project's designated bug or continuation record.

If reproduction remains unavailable, distinguish a proposed fix from a verified correction. Timeouts and incomplete measurements remain unknown.
Files in this package (2)
  • SKILL.md 2 KB
  • agents/openai.yaml 1 KB

Versions

The database has no other skills named evidence-driven-debugging.

Database snapshot: 13.11.2026 · package version 713a3727d018 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100debugging
    Systematic 5-step workflow (Reproduce → Isolate → Identify → Fix → Verify) for finding and fixing bugs in code. Use when the user reports a crash, error, stack trace, unexpected output, regression ("used to work"), flaky behavior, or performance issue — in JavaScript, Java, or…
  • 90debugging-diagnosis
    Diagnose and fix bugs through reproduction, minimization, hypotheses, instrumentation, targeted fixes, and regression coverage. Use when the user reports failing behavior, a broken test, runtime error, flaky workflow, or asks for debugging before implementation.
  • 90systematic-debugging
    Diagnose and fix a reproducible defect through observed state and competing hypotheses. Use for bugs, regressions, crashes, failing tests, build failures, hangs, or wrong output; do not use for feature design, speculative cleanup, or ordinary implementation.
  • 100debugging-specialist
    Diagnoses defects with a hypothesis-driven method: reproduce, isolate, form falsifiable hypotheses, test them with evidence, fix the root cause with a failing test first. Use for bugs, failing tests and unexpected behaviour.
  • 100systematic-debugging
    Find the root cause before changing anything: read the error, reproduce, gather evidence, rank hypotheses, test one at a time, then fix at the source with a failing test first. Use for any bug, test failure, build failure, flaky or intermittent behavior, performance regression…
  • 100debugger
    Systematic debugging methodology for diagnosing failures and root cause analysis. Triggers on: 2+ failed fix attempts, 'ultradebug', 'uld', debugging in circles, complex system failures, intermittent bugs.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.