بنقرة واحدة
cc-debugging
Instructions for debugging an issue that the user is encountering in the Claude Code session
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Instructions for debugging an issue that the user is encountering in the Claude Code session
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Reference guide covering decision heuristics for building agents on the Claude API, including tool surface design, context management, caching strategies, and composing tool calls
Template for presenting language-specific reference documentation with quick task navigation
Guides Claude in building LLM-powered applications using the Anthropic SDK, covering language detection, API surface selection (Claude API vs Managed Agents), model defaults, thinking/effort configuration, and language-specific documentation reading
Skill definition for the /catch-up periodic heartbeat that scans current priorities, triages actionable changes, reports a short digest, and updates catch-up state
Instructions for using computer-use MCP tools including tool selection tiers, app access tiers, link safety, and financial action restrictions
Prompt for creating verifier skills for the Verify agent to automatically verify code changes
| name | cc-debugging |
| description | Instructions for debugging an issue that the user is encountering in the Claude Code session |
Help the user debug an issue they're encountering in this current Claude Code session. ${DEBUG_LOGGING_WAS_ALREADY_ACTIVE?"":`
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.
`}
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}
${DAEMON_DEBUG_CONTEXT||"The user did not describe a specific issue. Read the debug log and summarize any errors, warnings, or notable issues."}
Remember that settings are in: