debugging-diagnosis
/debugging-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.
- Author
- stark-ai-de ↗
- Repository
- agent-skills ↗
- Licence
- Apache-2.0
- Last repository change
- 21.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
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.
Original author description
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.
How it works
- Goal
- When to use
- When not to use
- Inputs to inspect
- Workflow
- Safety rules
- References
- Scripts
- Output format
- Completion criteria
SKILL.md preview
--- name: debugging-diagnosis description: 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. license: Apache-2.0 metadata: author: stark-ai-de category: engineering-workflows internal: true version: "0.1.0" --- # Debugging Diagnosis ## Goal Find the smallest proven cause of a bug, fix it, and leave regression coverage or clear validation evidence. ## When to use - The user reports a bug, failing test, runtime error, broken workflow, or flaky behavior. - A prior fix was speculative and needs a reproducible diagnosis. - The task needs root cause analysis before a code change. ## When not to use - The user asks for a pure design plan with no failing behavior. - The task is a known mechanical edit with an obvious validation command. - The user asks for a broad repo audit rather than a specific failure. ## Inputs to inspect - Exact error text, logs, screenshots, failing test output, or reproduction steps. - Recent diffs and `git status --short`. - Relevant package scripts, test commands, CI workflow, issue context, and domain docs if present. - Existing tests around the failing behavior. ## Workflow 1. Establish the failure in the current environment or state what cannot be reproduced. 2. Minimize the reproduction to the smallest command, input, route, component, or test case. 3. Form one or more falsifiable hypotheses and inspect only the files needed to test them. 4. Add temporary instrumentation only when it answers a specific question; remove it before completion. 5. Fix the smallest cause that explains the reproduction. 6. Add or update regression coverage at the observable behavior boundary. 7. Re-run the reproduction and the smallest relevant validation command. ## Safety rules - Do not make broad rewrites before proving the failure path. - Do not hide a failure by weakening assertions, swallowing errors, or deleting coverage. - Do not leave debug logs, probes, or temporary scripts behind. - Do not claim a bug is fixed without a passing reproduction or an explicit validation limitation. ## References No bundled references. If the repo has `docs/agents/validation.md` or domain docs, inspect them when selecting validation commands or domain-specific expected behavior. ## Scripts No bundled scripts. ## Output format Return: 1. Reproduction command or reason reproduction was unavailable 2. Root cause 3. Files changed 4. Regression coverage added 5. Validation commands and results 6. Remaining risks ## Completion criteria - The failure is reproduced or the reproduction gap is explicit. - The root cause is tied to observed evidence. - The fix is narrow and validated. - Regression coverage exists unless the repo has no suitable test surface, in which case the reason is stated. ## Failure modes - If the failure cannot be reproduced, preserve evidence and ask for the missing input rather than guessing. - If multiple causes are plausible, test them one at a time. - If validation is too expensive, run the smallest reliable subset and name the unrun command.
Versions
The database has no other skills named debugging-diagnosis.
Database snapshot: 13.11.2026 · package version d2fa1e6f0d76 (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
- 100diagnose
Debug coding failures through reproduction, ranked hypotheses, narrow fixes, and verification. Use when a bug, regression, flaky test, performance failure, or inconsistent behavior is broken, slow, throwing, or hard to reproduce and the task needs disciplined diagnosis instead of guessed fixes. - 90diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression. - 100fix-bug
Diagnoses and fixes bugs using a test-first workflow (reproduce, diagnose, fix). Use this skill whenever the user reports a bug, describes unexpected behavior, or asks to investigate or fix a defect. Even if the user says "something's broken", "this isn't working", "fix this… - 100systematic-debugging
Finds the root cause of a defect by first building a fast reproduction that goes red on the bug, then minimizing it, ranking falsifiable hypotheses, instrumenting, and fixing with a regression test. Use when facing a bug, failing or flaky test, crash, error message, stack trace,… - 90diagnosing-bugs
Diagnose bugs and performance regressions through reproduction, ranked hypotheses and causal checks. Use for failures, slow behavior or "debug this"; an explicitly selected host debug command keeps its route. - 100diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce -> minimise -> hypothesise -> instrument -> fix -> regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.