error-detective
Debug errors systematically with TRACE framework
Debugging errors takes too long when you do not have a clear process. This skill provides a systematic TRACE framework to trace, read, analyze, check, and execute fixes for any error across Python, JavaScript, Java, and Go.
スキルZIPをダウンロード
Claudeでアップロード
設定 → 機能 → スキル → スキルをアップロードへ移動
オンにして利用開始
テストする
「error-detective」を使用しています。 Debug this Python error: Traceback (most recent call last): File app.py line 45 in get_user user.profile.to_dict() AttributeError: 'NoneType' object has no attribute 'to_dict'
期待される結果:
- Error Type: AttributeError - None object accessed
- Root Cause: user.profile is None, likely user has no profile
- Fix: Add null check or ensure profile creation
- Language: Python
- Severity: Runtime error
「error-detective」を使用しています。 Analyze this JavaScript stack trace from my Node.js app
期待される結果:
- Error Type: ReferenceError - Variable not defined
- Location: line 12 in auth.js
- Root Cause: Variable 'token' used before declaration
- Fix: Declare variable with let or const before use
「error-detective」を使用しています。 Why did my application work yesterday but fail today
期待される結果:
- Check recent git changes with 'git diff'
- Review dependency updates in package.json
- Verify environment variables are set
- Look for time-dependent logic or cron jobs
セキュリティ監査
低リスクThis is a documentation and methodology skill with a Python helper script for stack trace parsing. All 260 static findings are false positives - the scanner misinterpreted markdown documentation examples as executable code. The skill does not execute commands, make network calls, or access credentials. File operations in debug_helper.py are limited to user-specified files and a local session directory.
低リスクの問題 (1)
リスク要因
📁 ファイルシステムへのアクセス (3)
⚡ スクリプトを含む (1)
品質スコア
作れるもの
Debug production errors
Debug crashes and exceptions in your code using systematic analysis techniques
Investigate failures
Analyze application logs and stack traces to find root causes of production incidents
Learn debugging skills
Develop systematic debugging habits with structured methodology and real examples
これらのプロンプトを試す
Help me debug this error using the TRACE framework. Error: [paste error message]
Parse and analyze this stack trace. Identify the root cause and fix. Stack trace: [paste stack trace]
Analyze these log entries for error patterns. What are the most common errors and their causes?
Compare how to debug [TypeError/NullPointerException/AttributeError] in Python, JavaScript, and Java
ベストプラクティス
- Always read the complete error message before debugging
- Reproduce the error consistently before attempting fixes
- Change one variable at a time when testing hypotheses
- Document your findings and solutions for future reference
回避
- Skipping error messages and guessing at the problem
- Making multiple changes before identifying the root cause
- Fixing symptoms without addressing the underlying issue
- Not verifying that the fix resolves the original error