systematic-debugging
（中文）Systematic Debugging
Overview
Random fixes waste time and create new bugs. Quick patches mask underlying issues.
Core principle: ALWAYS find root cause before attempting fixes. Symptom fixes are failure.
Violating the letter of this process is violating the spirit of debugging.
The Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
If you haven't completed Phase 1, you cannot propose fixes.
When to Use
More from jackiexiao/jackie-skills-dev
verification-before-completion
（中文）Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
9using-git-worktrees
（中文）Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
8requesting-code-review
（中文）Use when completing tasks, implementing major features, or before merging to verify work meets requirements
8receiving-code-review
（中文）Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
8test-driven-development
（中文）Use when implementing any feature or bugfix, before writing implementation code
8vercel-react-best-practices
Vercel Engineering的React和Next.js性能优化指南。在编写、审阅或重构React/Next.js代码时应使用此技能，以确保最佳性能模式。触发涉及React组件、Next.js页面、数据获取、捆绑优化或性能改进的任务。
8