debug:plugin-debug
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.
What this skill does
# plugin-debug Reference for the debug plugin's runtime behavior. Describes what data is saved, where it is stored, and how the SessionStart hooks operate. ## Plugin Purpose The debug plugin is a lightweight diagnostic tool for Claude Code plugin development. It verifies that: - Plugin installation and loading work correctly - The `CLAUDE_PLUGIN_ROOT` environment variable resolves properly - SessionStart hooks execute and produce expected output ## Data Written at Session Start The debug plugin's SessionStart hooks execute on every session event (startup, resume, clear, compact). The following data is produced: | Destination | Content | Persistence | | ---------------------------------------------- | -------------------------------------------- | ------------------------ | | `$XDG_STATE_HOME/claude-code-plugin/debug.txt` | `CLAUDE_PLUGIN_ROOT` absolute path | Overwritten each session | | stdout (additionalContext) | Structured context about debug plugin status | Conversation only | Default `XDG_STATE_HOME` is `~/.local/state` when the environment variable is not set. ### State File 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). ### Session Context 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. ## Environment Variables | Variable | Description | | -------------------- | ------------------------------------------------------------------------------------- | | `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`. | ## Diagnostic Workflow When troubleshooting plugin issues: 1. Check the system-reminder output at session start — confirm "Debug plugin active" appears 2. Read `$XDG_STATE_HOME/claude-code-plugin/debug.txt` to verify `CLAUDE_PLUGIN_ROOT` resolution 3. Compare the path in the file with the expected plugin installation directory 4. If the file is missing or empty, the SessionStart hook failed to execute — check hook registration in `hooks/hooks.json`
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.