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.
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
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.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
正在使用「debugging-and-error-recovery」。 A search test fails after a query change, but the user interface looks correct.
預期結果:
正在使用「debugging-and-error-recovery」。 A build fails with a missing import after a dependency update.
預期結果:
Check the module path, exported names, lockfile state, and dependency compatibility. Then run the focused test, full suite, and build.
正在使用「debugging-and-error-recovery」。 A runtime error appears only under concurrent requests.
預期結果:
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.
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
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.
作者
addyosmani授權
MIT
Skillstore 修訂
r2
版本提示
作者未聲明版本。
引用
5d5054f8a23586f9b500fece1cb613a9dffc787b
維護新鮮度
2026/9/19
使用量
2 次下載 · 0 次瀏覽
檔案結構
📄 SKILL.md
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.
依五大品質面向審查程式碼
程式碼變更可能隱藏正確性、安全性、架構、可讀性與效能問題。此 skill 採用結構化的審查流程，並產出依優先順序排列且可採取行動的意見。
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.
Harden Applications Against Security Risks
Security reviews can miss trust boundaries and unsafe data flows. This skill supplies threat-modeling prompts, OWASP patterns, and practical review checklists.
有系統地偵錯軟體問題
由 Asmayaseen
缺乏結構的錯誤修復會浪費時間，並可能掩蓋真正的失敗原因。此技能會引導 Claude、Codex 和 Claude Code 進行以證據為基礎的根本原因分析。
偵錯錯誤與根本原因
由 89jobrien
當證據分散在日誌、堆疊追蹤與服務之間時，錯誤和事件很難分流判斷。此技能會結構化診斷流程、解析日誌、識別模式，並引導最小修復。
Review Defects and Verify Root-Cause Repairs
由 aakashh242
Reviews can miss failure conditions or accept fixes without reliable evidence. Gauntlet guides scoped adversarial reviews, authorized repairs, and revision-bound verification within a finite budget.
建構可靠的測試自動化
由 89jobrien
薄弱的測試會拖慢發布並掩蓋回歸問題。此技能可引導測試策略、TDD、自動化、覆蓋率審查，以及 Playwright 網頁檢查。
更快找到程式碼脈絡
由 89jobrien
開發人員經常耗費時間追查程式碼為何存在，以及有哪些內容依賴它。這個技能會提示 Claude、Codex 或 Claude Code 在變更前收集相關圖譜知識、呼叫者、匯入項目和測試。
在整個程式碼庫中規劃可靠測試
由 0xDarkMatter
這項技能協助團隊選擇測試策略、mock、資料 fixture、覆蓋率 gate 和 CI 模式，而不混淆測試範圍。它為 Claude、Codex 和 Claude Code 提供針對單元、整合、端對端、TDD 與管線測試的結構化指引。