v2.1.71 (+10,211 tokens)

This commit is contained in:
Mike
2026-03-07 08:39:18 -07:00
parent 6decbe3db6
commit 10a9b4f650
25 changed files with 661 additions and 57 deletions
+9 -2
View File
@@ -1,8 +1,9 @@
<!--
name: 'Skill: Debugging'
description: Instructions for debugging an issue that the user is encountering in the Claude Code session
ccVersion: 2.1.30
ccVersion: 2.1.71
variables:
- DEBUG_LOGGING_WAS_ALREADY_ACTIVE
- DEBUG_LOG_PATH
- DEBUG_LOG_SUMMARY
- ISSUE_DESCRIPTION
@@ -13,7 +14,13 @@ variables:
# Debug Skill
Help the user debug an issue they're encountering in this current Claude Code session.
${DEBUG_LOGGING_WAS_ALREADY_ACTIVE?"":`
## Debug Logging Just Enabled
Debug logging was OFF for this session until now. Nothing prior to this /debug invocation was captured.
Tell the user that debug logging is now active at \`${DEBUG_LOG_PATH}\`, ask them to reproduce the issue, then re-read the log. If they can't reproduce, they can also restart with \`claude --debug\` to capture logs from startup.
`}
## Session Debug Log
The debug log for the current session is at: \`${DEBUG_LOG_PATH}\`
@@ -37,6 +44,6 @@ Remember that settings are in:
1. Review the user's issue description
2. The last ${LOG_LINE_COUNT} lines show the debug file format. Look for [ERROR] and [WARN] entries, stack traces, and failure patterns across the file
3. Consider launching the ${CLAUDE_CODE_GUIDE_SUBAGENT_NAME} subagent to understand the relevate Claude Code features
3. Consider launching the ${CLAUDE_CODE_GUIDE_SUBAGENT_NAME} subagent to understand the relevant Claude Code features
4. Explain what you found in plain language
5. Suggest concrete fixes or next steps