systematic-debugging
체계적인 디버깅 방법론 적용
متاح أيضًا من: Asmayaseen,ZhanlinCui,ChrisWiles,sickn33,CodingCossack,Cycleaddict,DYAI2025,davila7,obra,Doyajin174,Cygnusfear
체계적인 접근 없이 디버깅하면 시간을 낭비하고 새로운 버그가 발생합니다. 이 스킬은 수정을 시도하기 전에 근본 원인을 찾는 4단계 방법론을 제공하여 첫 번째 수정 성공률을 극적으로 향상시킵니다.
تنزيل ZIP المهارة
رفع في Claude
اذهب إلى Settings → Capabilities → Skills → Upload skill
فعّل وابدأ الاستخدام
اختبرها
استخدام "systematic-debugging". 사용자가 비밀번호를 재설정하려고 할 때 로그인 함수에서 'undefined is not a function' 오류가 발생합니다
النتيجة المتوقعة:
- Phase 1 - Investigation: Read stack trace to find exact line, reproduce by calling resetPassword(), check git log for auth module changes, trace where the undefined function is called
- Phase 2 - Pattern Analysis: Find working authentication code, compare import statements and dependencies, list all differences
- Phase 3 - Hypothesis: The resetPassword module is missing the validateEmail import, evidenced by undefined function at line 45
- Phase 4 - Implementation: Write failing test, add missing import, verify all tests pass
استخدام "systematic-debugging". 장바구니 총액 계산에서 테스트가 'Expected 5 but got 3' 오류와 함께 실패합니다
النتيجة المتوقعة:
- Phase 1 - Investigation: Read the full test error, locate the exact assertion, find the test setup code, reproduce the failure locally
- Phase 2 - Pattern Analysis: Compare with passing cart tests, identify differences in test setup and product data
- Phase 3 - Hypothesis: The discount calculation is not being applied because the coupon flag is being read before initialization
- Phase 4 - Implementation: Write failing test that verifies coupon flag initialization, reorder the initialization code, confirm all tests pass
التدقيق الأمني
آمنThis is a pure documentation skill containing only markdown instructions for systematic debugging methodology. No executable code, scripts, or file operations. All 14 static findings are false positives caused by the scanner misidentifying common English words ('Four', 'For') as cryptographic terms and legitimate debugging practices (checking git history) as system reconnaissance.
عوامل الخطر
🌐 الوصول إلى الشبكة (1)
📁 الوصول إلى نظام الملفات (1)
⚙️ الأوامر الخارجية (1)
درجة الجودة
ماذا يمكنك بناءه
효율적으로 버그 수정
새로운 버그 도입을 방지하기 위해 코드 변경 전에 근본 원인 분석 적용
테스트 실패 분석
테스트 실패를 체계적으로 조사하여 문제가 코드에 있는지 테스트에 있는지 판단
프로덕션 이슈 디버깅
진단 증거 수집과 가설 검증을 사용하여 배포 실패 진단
جرّب هذه الموجهات
Use systematic debugging methodology to investigate this issue. Apply the four phases: root cause investigation, pattern analysis, hypothesis testing, and implementation. Before proposing any fix, read error messages, reproduce consistently, check recent changes, and trace data flow.
A test is failing. Apply systematic debugging: read the full error message and stack trace, identify the exact assertion failure, compare with passing tests, form a hypothesis about the root cause, and verify with minimal code changes.
Previous debugging attempts failed. Apply systematic debugging from Phase 1: stop attempting quick fixes, question whether this is an architectural problem, gather fresh diagnostic evidence, and ask whether refactoring is needed.
A regression was introduced. Use systematic debugging: check git history for recent changes, backtrace data flow from the error, compare with similar working code, form a testable hypothesis, and implement a TDD fix.
أفضل الممارسات
- 항상 오류에서 역방향으로 데이터 흐름을 추적하여 잘못된 값이 발생한 위치를 찾으세요
- 근본 원인 패턴을 식별하기 위해 정상 코드와 손상된 코드를 비교하세요
- 가설을 검증할 때 한 번에 하나의 변수만 변경하세요
تجنب
- 근본 원인을 완전히 이해하지 않고 수정 제안하기
- 디버깅 중 여러 변경을 동시에 시도하기
- 진단 증거를 먼저 수집하지 않고 빠른 패치 적용하기