Habilidades debugging-and-error-recovery
📦

debugging-and-error-recovery

Revisión del contenido r1 Seguro ⚙️ Comandos externos🔑 Variables de entorno

Debug Failures at the Root Cause

Unstructured debugging causes repeated failures, wasted time, and fragile fixes. This skill provides a repeatable process for finding causes, validating fixes, and preventing regressions.

Compatible con: Claude Codex Code(CC)
🥉 78 Bronce

Instalar con mi Agente

Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.

Solicitud de agente
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.

Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.

Pruébalo

Usando "debugging-and-error-recovery". A pagination test started failing after a refactor. The error says the second page repeats an item from the first page.

Resultado esperado:

Reproduce the test, compare page boundaries, inspect cursor or offset logic, reduce the duplicate case, fix the boundary, and add a regression test.

Usando "debugging-and-error-recovery". The application builds locally but fails in CI with a missing module error.

Resultado esperado:

  • Confirm the exact module and import path from the CI log.
  • Compare dependency manifests, lockfiles, runtime versions, and case-sensitive paths.
  • Run the repository's clean install and build commands locally.
  • Add a verification step that catches the dependency mismatch before release.

Usando "debugging-and-error-recovery". A runtime chart sometimes renders a blank area without an error.

Resultado esperado:

Capture input and render state, log the data boundary, reproduce the malformed case, add an empty-state guard, and create a regression test.

Auditoría de seguridad

Seguro

All 32 static findings are false positives because they identify Markdown fences, example commands, a configuration lookup, or ordinary troubleshooting text rather than executable malware. No prompt injection, data-exfiltration intent, or malicious behavior was found in SKILL.md.

1
Archivos escaneados
301
Líneas analizadas
0
Elementos de revisión
0
Falsos positivos ignorados
La auditoría estática y semántica completada más reciente no detectó hallazgos de seguridad confirmados. Esto no demuestra que el skill no tenga efectos secundarios.
Auditado por: codex
Compartir y citar este informe

Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.

Abrir el informe versionado
Evaluación de seguridad

Copiar enlace del informe

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

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

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

Tarjeta para insertar

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

Cita APA

addyosmani. (2026). debugging-and-error-recovery security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-debugging-and-error-recovery/audits/1

Cita BibTeX

@techreport{addyosmani-addyosmani-debugging-and-error-recovery-2026, author = {addyosmani}, title = {debugging-and-error-recovery security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/addyosmani-debugging-and-error-recovery/audits/1}, 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 1)" version: "unspecified" type: report authors: - name: "addyosmani" date-released: "2026-09-12" url: "https://skillstore.io/skills/addyosmani-debugging-and-error-recovery/audits/1" identifiers: - type: other value: "skillstore:addyosmani-debugging-and-error-recovery:audit:1" description: "Skillstore immutable audit report identifier"

Puntuación de Skillstore

Por qué esta puntuación Confianza de la evidencia: Medio
55
Arquitectura
85
Mantenibilidad
87
Contenido
65
Comunidad
91
Cumplimiento de la especificación

Lo que puedes crear

Triage a failing test

Reproduce the failure, isolate the smallest case, identify the cause, and add a regression test.

Investigate a broken build

Classify the build error, inspect the cited layer, verify dependencies, and confirm the complete build afterward.

Stabilize a production bug

Preserve evidence, localize runtime behavior, apply a durable fix, and verify the original scenario end to end.

Prueba estos prompts

Start a Basic Triage
Use the debugging workflow for this issue: [describe the failure]. Ask for missing reproduction steps and evidence, then identify the next diagnostic action.
Analyze a Test Failure
Triage this failing test using reproduce, localize, reduce, fix, guard, and verify. Test: [name]. Error: [output]. Recent change: [change].
Find a Regression Commit
Isolate the regression in [repository or component]. Compare known-good and failing states, create a minimal reproduction, and define focused verification commands.
Lead an Incident Investigation
Lead this incident: [symptoms, timeline, logs, and impact]. Separate facts from hypotheses, identify needed evidence, propose a reversible fix, and define safeguards.

Mejores prácticas

  • Reproduce the failure before changing code, and preserve logs, inputs, and conditions.
  • Prefer the smallest failing case and fix the root cause instead of masking the symptom.
  • Verify the original scenario, the full test suite, and relevant build checks after the fix.

Evitar

  • Do not skip a failing test to continue feature work.
  • Do not guess at a fix without confirming the failure and its evidence.
  • Do not make unrelated changes while investigating a defect.

Preguntas frecuentes

When should I use this skill?
Use it when tests, builds, runtime behavior, or production workflows fail unexpectedly.
Does it execute debugging commands?
No. It provides command examples and asks you to adapt them to the repository.
What should I provide first?
Provide the exact error, reproduction steps, recent changes, environment details, and relevant logs.
How does it handle intermittent bugs?
It recommends targeted instrumentation, controlled delays, isolation, monitoring, and documentation of observed conditions.
Does it support production incidents?
Yes. It covers evidence preservation, runtime triage, safe fixes, end-to-end verification, and recurrence safeguards.
Is it a substitute for security review?
No. It supports technical diagnosis but does not replace security, privacy, incident response, or change-control processes.

Detalles del desarrollador

Licencia

MIT

Revisión de Skillstore

r1

Aviso de versión

El autor no declaró una versión.

Ref.

5526951beaeca22519572a471618555839b53b05

Actualidad del mantenimiento

14/9/2026

Uso

0 descargas · 0 vistas

Estructura de archivos

📄 SKILL.md

Más de addyosmani

Ver todo
Ver todo