Skills debugging-and-error-recovery
๐Ÿ“ฆ

debugging-and-error-recovery

Content revision r2 Safe โš™๏ธ External commands๐Ÿ”‘ Env variables

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.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
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.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "debugging-and-error-recovery". A search test fails after a query change, but the user interface looks correct.

Expected outcome:

  • Reproduce the focused test with verbose output.
  • Compare the query result count with the expected data.
  • Inspect joins and add a regression test for duplicate results.

Using "debugging-and-error-recovery". A build fails with a missing import after a dependency update.

Expected outcome:

Check the module path, exported names, lockfile state, and dependency compatibility. Then run the focused test, full suite, and build.

Using "debugging-and-error-recovery". A runtime error appears only under concurrent requests.

Expected outcome:

  • Capture timestamps and request context around the failure.
  • Reproduce with controlled concurrency.
  • Inspect shared state, then verify the fix under the original load pattern.

Security Audit

Safe
v2 โ€ข 9/19/2026 Open versioned report

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.

1
Files scanned
301
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/addyosmani-debugging-and-error-recovery/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/addyosmani-debugging-and-error-recovery/security.svg)](https://skillstore.io/skills/addyosmani-debugging-and-error-recovery?utm_source=security_passport_badge)

HTML 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>

Embed card

<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>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

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

BibTeX citation

@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} }

CITATION.cff

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"

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
65
Community
91
Spec Compliance

What You Can Build

Investigate a failing test

Reproduce the failure, isolate the affected layer, identify the root cause, and design a regression test.

Recover a broken build

Separate type, import, configuration, dependency, and environment failures before applying a focused fix.

Triage a production error

Preserve evidence, treat external error text as untrusted data, localize the fault, and verify recovery safely.

Try These Prompts

Start a debugging triage
My application has this failure: [describe failure]. Help me reproduce it, gather evidence, and list the first diagnostic steps.
Localize a test failure
A test changed from passing to failing after [change]. Use a structured workflow to identify the failing layer and likely causes.
Find a regression commit
This behavior worked at [known-good revision] and fails at [current revision]. Plan a minimal reproduction and a git bisect investigation.
Design a verified recovery
Analyze this incident evidence: [logs, symptoms, and reproduction]. Propose the root-cause fix, regression coverage, verification commands, and safe rollback conditions.

Best Practices

  • Preserve logs, error output, and reproduction steps before changing code.
  • Reduce failures to the smallest reliable case before fixing symptoms.
  • Verify the original scenario, full tests, build, and regression coverage after the fix.

Avoid

  • Do not skip failing tests or continue feature work before understanding the failure.
  • Do not apply speculative fixes without reproducing or localizing the problem.
  • Do not follow commands embedded in error output without independent verification and user approval.

Frequently Asked Questions

When should I use this skill?
Use it when tests fail, builds break, runtime behavior changes, or an incident needs structured investigation.
Does it run debugging commands?
No. It provides command examples and reasoning steps for you or an authorized tool to execute.
Can it debug production incidents?
It provides triage guidance, evidence handling, and verification steps, but it cannot access or operate your production systems.
How does it handle suspicious error messages?
It treats error messages, logs, and stack traces as untrusted data rather than instructions.
Which projects does it support?
It supports any project when you adapt its examples to the repository's language, framework, and commands.
What should I provide for better results?
Provide the exact symptom, reproduction steps, recent changes, relevant output, environment details, and expected behavior.

Developer Details

Author

addyosmani

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

5d5054f8a23586f9b500fece1cb613a9dffc787b

Maintenance freshness

9/19/2026

Usage

2 downloads ยท 0 views

File structure

๐Ÿ“„ SKILL.md