Debugging Wizard
技能 已验证 活跃Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting crashes, or performing log analysis, error investigation, or root cause analysis.
To systematically isolate and resolve bugs in any codebase by applying a structured methodology and leveraging common debugging tools and techniques.
功能
- Parses error messages and stack traces
- Guides users through systematic bug reproduction
- Provides hypothesis-driven testing methodology
- Documents common debugging tools and commands
- Offers structured approach to root cause analysis
使用场景
- Investigating errors and unexpected behavior
- Analyzing stack traces to find failure points
- Troubleshooting application crashes
- Performing log analysis for root cause identification
非目标
- Performing code fixes automatically
- Acting as a linter or static analysis tool
- Replacing IDE debuggers (but guiding their use)
工作流
- Reproduce the issue
- Isolate the failing case
- Hypothesize and test theories
- Implement and verify the fix
- Add safeguards against regression
实践
- Systematic debugging methodology
- Root cause analysis
- Error message parsing
- Debugging tool usage
安装
请先添加 Marketplace
/plugin marketplace add jeffallan/claude-skills/plugin install claude-skills@fullstack-dev-skills质量评分
已验证类似扩展
Trajectory Review
99对失败的代理轨迹进行事后诊断。将第一个无法恢复的步骤分类为九种失败类别之一（计划遵循性、幻觉信息、无效工具调用、误读工具输出、意图-计划不匹配、意图不明确、意图不支持、护栏触发、系统故障），并生成有证据支持的根本原因报告。
Safe Debug
99用于深度学习研究工作的可信赖的调试技能。当用户粘贴了堆栈跟踪、终端错误、CUDA OOM、检查点加载失败、形状不匹配、NaN 损失症状或训练失败，并希望在任何修补之前进行保守诊断时使用。请勿用于广泛重构、推测性适配、自动探索性修补或通用存储库熟悉。
Migrate Validate
100Validate pending migrations for foreign key consistency, rollback safety, and best practices
Semgrep Rule Creator
100Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Use when writing Semgrep rules or building custom static analysis detections.
Moyu (摸鱼)
100감지된 과잉 엔지니어링 패턴: (1) 사용자가 명시적으로 요청하지 않은 코드나 파일을 수정할 때 (2) 요청되지 않은 새로운 추상화 계층(클래스, 인터페이스, 팩토리, 래퍼)을 생성할 때 (3) 요청되지 않은 주석, 문서, JSDoc, 타입 주석을 추가할 때 (4) 요청되지 않은 새로운 종속성을 도입할 때 (5) 최소 편집 대신 파일 전체를 다시 작성할 때 (6) diff 범위가 사용자의 요청을 명백히 초과할 때 (7) 사용자가 "너무 많아", "거기는 건드리지 마", "X만 변경해", "간단하게", "그만"과 같은 신호를 보낼 때 (8) 발생할 수 없는 시나리오에 대한 오류 처리, 유효성 검사, 방어적 코드를 추가할 때 (9) 요청되지 않은 테스트, 설정 스캐폴딩, 문서를 생성할 때
使用我的浏览器
100当工作依赖于用户实时浏览器会话或可见的渲染状态，而不是静态抓取时使用，尤其是在浏览器调试上下文或 DevTools 选择的元素或请求、登录仪表板或 CMS 流程、localhost 应用、上传、下载、媒体检查、DOM 或 iframe 检查、Shadow DOM，或看起来像软 404、身份验证墙、反机器人检查或速率限制的浏览器故障时。