systematic-debugging
버그 수정 전에 근본 원인 찾기
متاح أيضًا من: Asmayaseen,DMJGilbert,ZhanlinCui,ChrisWiles,sickn33,CodingCossack,Cycleaddict,DYAI2025,davila7,obra,Cygnusfear
버그 수정은 종종 증상만 다룰 때 실패합니다. 이 4단계 디버깅 프레임워크는 해결책을 시도하기 전에 근본 원인을 이해하도록 보장합니다. 디버깅 시간을 줄이고 반복되는 문제를 방지합니다.
تنزيل ZIP المهارة
رفع في Claude
اذهب إلى Settings → Capabilities → Skills → Upload skill
فعّل وابدأ الاستخدام
اختبرها
استخدام "systematic-debugging". My API returns 500 errors for user ID 12345 but works for other users
النتيجة المتوقعة:
- ## Problem: 500 Error for Specific User
- ## Phase 1 Investigation:
- - Error message from server
- - Recent git commits checked
- - Data flow traced from user through API
- ## Phase 2 Pattern Analysis:
- - User ID 12346 works correctly
- - Difference: User 12345 has specific data or permission issue
- ## Hypothesis:
- 1. User 12345 has corrupted data in database
- 2. Missing permission for specific user in ACL
- ## Next Steps:
- Test each hypothesis one at a time with minimal changes
استخدام "systematic-debugging". The login feature stopped working after the recent deployment
النتيجة المتوقعة:
- ## Problem: Login Feature Broken After Deployment
- ## Phase 1 Investigation:
- - Error type: Authentication error or timeout
- - Deployment timestamp identified
- - Affected users: All or specific groups checked
- ## Phase 2 Pattern Analysis:
- - Pre-deployment: Login worked for all users
- - Post-deployment: Login fails consistently
- - Recent deployment commits reviewed
- ## Hypothesis:
- 1. Environment variable missing from config
- 2. Database migration failed
- 3. Authentication service version mismatch
استخدام "systematic-debugging". Memory usage keeps growing over time until the application crashes
النتيجة المتوقعة:
- ## Problem: Memory Leak Detected
- ## Phase 1 Investigation:
- - Pattern: Gradual memory increase over hours
- - Trigger: Specific user actions identified
- - Recovery: Restart clears memory confirmed
- ## Phase 2 Pattern Analysis:
- - Stable state: Fresh start memory usage measured
- - Leaking state: Memory growth pattern tracked
- - Components with active services identified
- ## Hypothesis:
- 1. Event listener not removed in cleanup code
- 2. Cache growing without limits
- 3. Object references retained in memory
التدقيق الأمني
آمنPure prompt-based skill with no executable code. All 23 static findings are false positives caused by the scanner misinterpreting Korean documentation text and JSON metadata as security patterns. Contains only debugging methodology documentation.
عوامل الخطر
🌐 الوصول إلى الشبكة (1)
📁 الوصول إلى نظام الملفات (1)
درجة الجودة
ماذا يمكنك بناءه
프로덕션 문제 디버깅
근본 원인 분석을 사용하여 프로덕션 또는 개발 환경의 버그를 체계적으로 진단
테스트 실패 조사
테스트 실패를 분석하여 실제 버그인지 테스트 문제를 나타내는지 확인
배포 실패 디버깅
다중 구성 요소 시스템 진단을 통해 배포 실패 추적
جرّب هذه الموجهات
버그를 발견했습니다: [문제 설명]. 체계적 디버깅 프레임워크를 사용하여 근본 원인을 찾는 것을 도와주세요.
내 테스트 [테스트 이름]이(가) 오류와 함께 실패합니다: [오류 메시지]. Phase 1 조사 단계를 따라 무슨 일이 일어나는지 이해하는 것을 도와주세요.
أفضل الممارسات
- Always reproduce the issue consistently before attempting fixes
- Change only one variable at a time when testing hypotheses
- Document evidence, attempts, and results for future reference
تجنب
- Applying quick fixes without understanding root cause
- Making multiple changes simultaneously
- Skipping the investigation phases and guessing