mkusaka/debugging
skills/debugging/SKILL.md
Instructions for debugging an issue that the user is encountering in the Claude Code session
$ install --global
skillsauthnpx skillsauth add mkusaka/ccskills debuggingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 29, 2026, 7:49 AM210.0s1 file scanned
SKILL.md
- name:
- debugging
- description:
- Instructions for debugging an issue that the user is encountering in the Claude Code session
- originalName:
- Skill: Debugging
- ccVersion:
- 2.1.122
- sourceUrl:
- https://github.com/Piebald-AI/claude-code-system-prompts/blob/main/system-prompts/skill-debugging.md
- owner:
- Piebald-AI
- repo:
- claude-code-system-prompts
- ref:
- main
- path:
- system-prompts/skill-debugging.md
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}
${DEBUG_LOG_SUMMARY}
For additional context, grep for [ERROR] and [WARN] lines across the full file.
${ISSUE_DESCRIPTION}
Issue Description
${DAEMON_DEBUG_CONTEXT||"The user did not describe a specific issue. Read the debug log and summarize any errors, warnings, or notable issues."}
Settings
Remember that settings are in:
- user - ${GET_SETTINGS_FILE_PATH_FN("userSettings")}
- project - ${GET_SETTINGS_FILE_PATH_FN("projectSettings")}
- local - ${GET_SETTINGS_FILE_PATH_FN("localSettings")}
Instructions
- Review the user's issue description
- 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
- Consider launching the ${CLAUDE_CODE_GUIDE_SUBAGENT_NAME} subagent to understand the relevant Claude Code features
- Explain what you found in plain language
- Suggest concrete fixes or next steps
Related Skills
mkusaka/design-sync-storybook-source-shape
development
VerifiedTrustedCommunity
Shape-specific /design-sync instructions for syncing a React design system from Storybook stories and built package output
6SKILL.mdUpdated Jun 4, 2026
mkusaka/design-sync-slash-command
development
VerifiedTrustedCommunity
Skill definition for syncing a React design system to claude.ai/design, including project selection, source-shape detection, converter configuration, validation, upload planning, and self-check behavior
6SKILL.mdUpdated Jun 4, 2026
mkusaka/design-sync-package-source-shape
development
VerifiedTrustedCommunity
Shape-specific /design-sync instructions for syncing a React design system from a built package without Storybook
6SKILL.mdUpdated Jun 4, 2026
mkusaka/claude-code-configuration-guide
development
VerifiedTrustedCommunity
Skill instructions for answering Claude Code configuration questions by checking the running build, bundled references, and current documentation
6SKILL.mdUpdated May 30, 2026