菜单
This skill should be used when the user asks about 'debug plugin behavior', 'what does the debug plugin save', 'debug plugin files', 'where does debug plugin write', or mentions debug plugin data storage and session artifacts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when the user asks to "lint AI assistant config", "check AGENTS.md", "validate SKILL.md", "agnix lint", or wants to detect and fix best-practice violations in Claude Code / agent configuration files.
This skill is the mandatory reference for all Claude Code hook creation. Use cc-hooks-ts for every hook. This skill should be used when the user asks to "create a hook", "add a hook", "write a hook", "implement a hook", "rewrite hooks in TypeScript", "use cc-hooks-ts", or needs to build any Claude Code hook — cc-hooks-ts is always required regardless of whether explicitly mentioned.
Auto-activate CCS CLI delegation for deterministic tasks. Parses user input, auto-selects optimal profile (glm/kimi/custom) from ~/.ccs/config.json, enhances prompts with context, executes via `ccs {profile} -p "task"` or `ccs {profile}:continue`, and reports results. Triggers on "use ccs [task]" patterns, typo/test/refactor keywords. Excludes complex architecture, security-critical code, performance optimization, breaking changes.
This skill should be used when the user asks to "handoff from CCS", "Claude Codeの作業を引き継ぐ", "rate limit handoff", "context overflow", or wants to resume interrupted work from another CCS profile session.
This skill should be used when the user asks for "code review", "レビューして", "review this diff", "実装をレビュー", or wants rigorous review of recently created artifacts.
Direct utility reference for code-review PR scripts. Documents unresolved-thread, comment, CI-status, and CI-log helpers used by higher-level PR workflows.
| name | debug:plugin-debug |
| description | This skill should be used when the user asks about 'debug plugin behavior', 'what does the debug plugin save', 'debug plugin files', 'where does debug plugin write', or mentions debug plugin data storage and session artifacts. |
Reference for the debug plugin's runtime behavior. Describes what data is saved, where it is stored, and how the SessionStart hooks operate.
The debug plugin is a lightweight diagnostic tool for Claude Code plugin development. It verifies that:
CLAUDE_PLUGIN_ROOT environment variable resolves properlyThe debug plugin's SessionStart hooks execute on every session event (startup, resume, clear, compact). The following data is produced:
$XDG_STATE_HOME/claude-code-plugin/debug.txt — CLAUDE_PLUGIN_ROOT absolute path
Default XDG_STATE_HOME is ~/.local/state when the environment variable is not set.
Written by the SessionStart hook at $XDG_STATE_HOME/claude-code-plugin/debug.txt. Contains the resolved CLAUDE_PLUGIN_ROOT path as a single line. Overwritten on every session start — only the most recent value is retained.
Use this file to verify that CLAUDE_PLUGIN_ROOT resolves correctly outside of the Claude Code session (e.g., from a separate terminal).
The SessionStart hook outputs a structured context message via additionalContext, which Claude Code injects as a <system-reminder>. This informs the AI that the debug plugin is active and provides key environment details. No command output is shown — only the context message is passed.
CLAUDE_PLUGIN_ROOT — Absolute path to the debug plugin directory. Set by Claude Code for all plugin hooks.XDG_STATE_HOME — Base directory for state data. Falls back to ~/.local/state.When troubleshooting plugin issues:
$XDG_STATE_HOME/claude-code-plugin/debug.txt to verify CLAUDE_PLUGIN_ROOT resolutionhooks/hooks.json