Compétences debugging-and-error-recovery
📦

debugging-and-error-recovery

Révision du contenu r2 Sûr ⚙️ Commandes externes🔑 Variables d’environnement

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.

Prend en charge: Claude Codex Code(CC)
Maintain this Skill? Claim it 🥉 78 Bronze

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent
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.

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Détail Markdown GET /skills/addyosmani-debugging-and-error-recovery.md manifest signé GET /api/skills/addyosmani-debugging-and-error-recovery/manifest lockfile signé GET /api/skills/addyosmani-debugging-and-error-recovery/lockfile

Tester

Utilisation de « debugging-and-error-recovery ». A search test fails after a query change, but the user interface looks correct.

RĂ©sultat attendu:

  • 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.

Utilisation de « debugging-and-error-recovery ». A build fails with a missing import after a dependency update.

RĂ©sultat attendu:

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

Utilisation de « debugging-and-error-recovery ». A runtime error appears only under concurrent requests.

RĂ©sultat attendu:

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

Audit de sécurité

Sûr
v2 • 19/09/2026 Ouvrir le rapport versionné

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
Fichiers analysés
301
Lignes analysées
0
Éléments à examiner
0
Faux positifs ignorés

Facteurs de risque

⚙️ Commandes externes (26)
SKILL.md:25-32 SKILL.md:32-44 SKILL.md:44-51 SKILL.md:51-55 SKILL.md:55-73 SKILL.md:73-76 SKILL.md:76-85 SKILL.md:85-91 SKILL.md:91-99 SKILL.md:99-102 SKILL.md:102-109 SKILL.md:109-125 SKILL.md:125-134 SKILL.md:134-142 SKILL.md:142-150 SKILL.md:150-158 SKILL.md:158-170 SKILL.md:170-176 SKILL.md:176-186 SKILL.md:186-190 SKILL.md:190-197 SKILL.md:197-201 SKILL.md:201-212 SKILL.md:212-218 SKILL.md:218-223 SKILL.md:223-241
🔑 Variables d’environnement (2)
SKILL.md:221 SKILL.md:221
Le dernier audit statique et sémantique terminé n’a détecté aucun constat de sécurité confirmé. Cela ne prouve pas que le skill est sans effets secondaires.
Audité par: codex Voir l’historique des audits →
Partager et citer ce rapport

Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.

Ouvrir le rapport versionné
Évaluation de sécurité

Copier le lien du rapport

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

Badge Markdown

[![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)

Badge HTML

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

Carte intégrable

<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>
Citations académiques (APA · BibTeX · CFF)

Citation APA

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

Citation BibTeX

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

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen
55
Architecture
85
Maintenabilité
87
Contenu
65
Communauté
91
Conformité aux spécifications

Ce que vous pouvez créer

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.

Essayez ces 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.

Bonnes pratiques

  • 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.

Éviter

  • 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.

Foire aux 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.

Détails du développeur

Auteur

addyosmani

Licence

MIT

RĂ©vision Skillstore

r2

Avis de version

L’auteur n’a déclaré aucune version.

DĂ©pĂ´t

https://github.com/addyosmani/agent-skills/tree/c004a74784a08295d52749b04cda634125b9a581/skills/debugging-and-error-recovery

RĂ©f

5d5054f8a23586f9b500fece1cb613a9dffc787b

RĂ©cence de maintenance

19/09/2026

Utilisation

2 téléchargements · 0 vues

Structure de fichiers

đź“„ SKILL.md