Debug Errors with a Root-Cause Workflow
Debugging failures by guesswork wastes time and can hide the real cause. This skill provides a repeatable process for reproducing, isolating, fixing, and verifying problems.
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
Review the Skillstore skill "debugging-and-error-recovery" from https://skillstore.io/skills/addyosmani-debugging-and-error-recovery.md and its manifest at https://skillstore.io/api/skills/addyosmani-debugging-and-error-recovery/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
„debugging-and-error-recovery“ wird verwendet. A search test fails after a query change, but the user interface looks correct.
Erwartetes Ergebnis:
„debugging-and-error-recovery“ wird verwendet. A build fails with a missing import after a dependency update.
Erwartetes Ergebnis:
Check the module path, exported names, lockfile state, and dependency compatibility. Then run the focused test, full suite, and build.
„debugging-and-error-recovery“ wird verwendet. A runtime error appears only under concurrent requests.
Erwartetes Ergebnis:
All 32 static findings are false positives caused by Markdown code fences, illustrative shell commands, template literals, configuration examples, or checklist text. The skill provides defensive debugging guidance and includes explicit instructions to treat external error output as untrusted data.
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
https://skillstore.io/skills/addyosmani-debugging-and-error-recovery/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/addyosmani-debugging-and-error-recovery?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/addyosmani-debugging-and-error-recovery?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-debugging-and-error-recovery/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/addyosmani-debugging-and-error-recovery.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>addyosmani. (2026). debugging-and-error-recovery security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-debugging-and-error-recovery/audits/2@techreport{addyosmani-addyosmani-debugging-and-error-recovery-2026,
author = {addyosmani},
title = {debugging-and-error-recovery security audit report (audit version 2)},
institution = {Skillstore},
year = {2026},
number = {2},
url = {https://skillstore.io/skills/addyosmani-debugging-and-error-recovery/audits/2},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "debugging-and-error-recovery security audit report (audit version 2)"
version: "unspecified"
type: report
authors:
- name: "addyosmani"
date-released: "2026-09-19"
url: "https://skillstore.io/skills/addyosmani-debugging-and-error-recovery/audits/2"
identifiers:
- type: other
value: "skillstore:addyosmani-debugging-and-error-recovery:audit:2"
description: "Skillstore immutable audit report identifier"
Reproduce the failure, isolate the affected layer, identify the root cause, and design a regression test.
Separate type, import, configuration, dependency, and environment failures before applying a focused fix.
Preserve evidence, treat external error text as untrusted data, localize the fault, and verify recovery safely.
My application has this failure: [describe failure]. Help me reproduce it, gather evidence, and list the first diagnostic steps.
A test changed from passing to failing after [change]. Use a structured workflow to identify the failing layer and likely causes.
This behavior worked at [known-good revision] and fails at [current revision]. Plan a minimal reproduction and a git bisect investigation.
Analyze this incident evidence: [logs, symptoms, and reproduction]. Propose the root-cause fix, regression coverage, verification commands, and safe rollback conditions.
Autor
addyosmaniLizenz
MIT
Skillstore-Revision
r2
Versionshinweis
Der Autor hat keine Version angegeben.
Ref.
5d5054f8a23586f9b500fece1cb613a9dffc787b
Aktualität der Wartung
19.9.2026
Nutzung
2 Downloads · 0 Aufrufe
Dateistruktur
📄 SKILL.md
Code anhand von fünf Qualitätsdimensionen überprüfen
Codeänderungen können Probleme hinsichtlich Korrektheit, Sicherheit, Architektur, Lesbarkeit und Performance verbergen. Dieser Skill wendet einen strukturierten Review-Prozess an und liefert priorisiertes, umsetzbares Feedback.
Clarify User Intent Before You Build
Underspecified requests cause teams to build the wrong outcome and discover misalignment late. This skill runs a focused, one-question interview that turns ambiguity into confirmed intent.
Plan Work Into Verifiable Tasks
Large or vague software work can hide dependencies, missing acceptance criteria, and verification gaps. This skill converts a specification into ordered task slices with checkpoints, scope guidance, and clear completion conditions.
Document Decisions and Architecture Clearly
Teams lose context when important technical decisions remain in chat, code comments, or individual memory. This skill turns architectural reasoning, API guidance, project instructions, and release changes into structured documentation.
Build Accessible, Production-Ready Frontends
Frontend work can become inconsistent, inaccessible, or difficult to maintain. This skill guides component architecture, responsive layouts, state handling, and polished user experiences.
Structure Better Context for Coding Agents
Coding agents lose accuracy when context is incomplete, stale, or excessive. This skill provides practical structures for focused sessions, durable rules, and reliable handoffs.
Softwareprobleme systematisch debuggen
von Asmayaseen
Unstrukturiertes Beheben von Bugs verschwendet Zeit und kann den eigentlichen Fehler verdecken. Dieser Skill führt Claude, Codex und Claude Code durch evidenzbasierte Ursachenanalyse.
Fehler und Ursachen debuggen
von 89jobrien
Fehler und Incidents sind schwer zu triagieren, wenn sich Hinweise über Logs, Stacktraces und Services verteilen. Dieser Skill strukturiert die Diagnose, parst Logs, erkennt Muster und leitet zu minimalen Fixes an.
Zuverlässige Testautomatisierung entwickeln
von 89jobrien
Schwache Tests verlangsamen Releases und verbergen Regressionen. Diese Skill unterstützt bei Teststrategie, TDD, Automatisierung, Coverage-Review und Playwright-Webprüfungen.
Codekontext schneller finden
von 89jobrien
Entwickler verlieren häufig Zeit damit nachzuvollziehen, warum Code existiert und was davon abhängt. Dieser Skill veranlasst Claude, Codex oder Claude Code dazu, vor Änderungen zugehöriges Graph-Wissen, Aufrufer, Importe und Tests zu sammeln.
Zuverlässige Tests in Ihrer gesamten Codebasis planen
von 0xDarkMatter
Dieser Skill hilft Teams, Teststrategien, Mocks, Daten-Fixtures, Coverage-Gates und CI-Muster auszuwählen, ohne Testebenen zu vermischen. Er bietet Claude, Codex und Claude Code strukturierte Orientierung für Unit-, Integrations-, End-to-End-, TDD- und Pipeline-Tests.
Bessere Go-Tests erstellen
von 89jobrien
Go-Teams benötigen konsistente Tests für Units, Integrationen, Mocks, Benchmarks und Coverage. Diese Skill bietet praktische Go-Testmuster, die Claude, Codex und Claude Code während der Entwicklung anwenden können.