技能 systematic-debugging

🔍

systematic-debugging

Name: systematic-debugging
Author: sickn33

低风险

系统化调试Bug

也可从以下获取: Cygnusfear,Cycleaddict,ZhanlinCui,DMJGilbert,Doyajin174,Asmayaseen,DYAI2025,davila7,CodingCossack,obra,ChrisWiles

停止浪费时间在随机修复上。本技能向AI助手传授一种结构化的调试方法论，在尝试修复之前先找到根本原因，将调试时间从数小时缩短到数分钟。

支持: Claude Codex Code(CC)

🥉 72 青铜

下载技能 ZIP

在 Claude 中上传

前往设置 → 功能 → 技能 → 上传技能

开启并开始使用

测试它

正在使用“systematic-debugging”。 The login button is not working. Can you fix it?

预期结果:

在提出修复方案之前，我需要调查根本原因。让我收集证据：点击按钮时出现什么错误？你能分享相关代码吗？这之前能正常工作吗？最近有什么更改？

正在使用“systematic-debugging”。 API returns 500 error on /users endpoint

预期结果:

按照系统化调试：首先，我会稳定复现以了解确切条件。然后检查可能导致此问题的最近更改，追踪从请求到错误的数据流，并在提出任何修复方案之前识别根本原因。

正在使用“systematic-debugging”。 Fix the null pointer exception in user-service.ts line 42

预期结果:

我会先调查根本原因。null值从哪里来的？是什么调用时传入了null？让我追溯调用栈找到源头，然后在源头处修复，而非在第42行添加防御性代码。

安全审计

低风险

v1 • 2/25/2026

All 126 static findings are false positives. The skill contains legitimate debugging methodology with example commands shown as educational content. JavaScript template literals were misidentified as shell execution. Environment variable checks are for NODE_ENV configuration. Keychain commands are debugging examples, not malicious access. No actual security risks found.

已扫描文件

1,264

分析行数

发现项

审计总数

低风险问题 (4)

condition-based-waiting-example.ts:36 condition-based-waiting-example.ts:79 condition-based-waiting-example.ts:128

JavaScript Template Literals Misidentified as Shell Execution

Backticks in TypeScript files are JavaScript template literals for string interpolation, not shell command execution. The static scanner misidentified these as Ruby/shell backtick execution.

SKILL.md:103-104

Diagnostic Commands Shown as Debugging Examples

Commands like 'security list-keychains' in SKILL.md are shown as examples of what to check when debugging code signing issues, not actual malicious keychain access.

defense-in-depth.md:58 root-cause-tracing.md:77

Standard Environment Variable Configuration Pattern

process.env.NODE_ENV access is a standard, safe pattern for detecting test environments and conditionally running test-specific code.

find-polluter.sh:22 find-polluter.sh:23 find-polluter.sh:30

Legitimate Test Debugging Scripts

The find-polluter.sh script uses standard bash command substitution and redirection for running tests and checking file state - a legitimate debugging utility.

审计者: claude

质量评分

架构

100

可维护性

内容

社区

安全

100

规范符合性

你能构建什么

修复反复出现的测试失败

当测试间歇性或持续失败时，使用系统化方法追踪原因，而非应用掩盖真正问题的随机修复。

调试生产环境事件

当生产环境问题时，按照结构化调查快速识别根本原因，而非在压力下猜测解决方案。

学习调试规范

新手开发者或AI助手可以学习一种经过验证的调试方法论，避免常见错误，如过早优化或仅修复症状。

试试这些提示

基本调试请求

I'm seeing this error: [paste error]. Please use systematic debugging to investigate the root cause before proposing any fixes.

多组件调试

We have a CI pipeline that signs, and deploys. The builds, signing step is failing. Use systematic debugging to trace which layer is causing the issue.

测试失败调查

This test [test name] is failing. Please follow the systematic debugging process to find why, then create a failing test case before fixing.

架构问题

I've tried three fixes for this issue and each revealed a new problem in a different place. Please use systematic debugging to determine if this is an architectural problem.