Claude Skills

Use when finding docs affected by code changes. Find documentation files related to changed source files using lib/collectors/docs-patterns.

This skill should be used when the user asks about "plan drift", "reality check", "comparing docs to code", "project state analysis", "roadmap alignment", "implementation gaps", or needs guidance on identifying discrepancies between documented plans and actual implementation state.

Use when coordinating multiple enhancers for /enhance command. Runs analyzers in parallel and produces unified report.

Use when validating task completion before shipping. Runs tests, build, and requirement checks. Returns pass/fail with fix instructions.

Use when improving general prompts for structure, examples, and constraints.

Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.

Use when running performance benchmarks, establishing baselines, or validating regressions with sequential runs. Enforces 60s minimum runs (30s only for binary search) and no parallel benchmarks.

Use when managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version.

Use when reviewing hooks for safety, timeouts, and correct frontmatter.

Use when generating the unified enhancement report from aggregated findings. Called by orchestrator after all enhancers complete.

Use when user asks to \"create repo map\", \"generate repo map\", \"update repo map\", \"repo map status\", or \"map symbols/imports\". Builds and validates an AST-based repo map using ast-grep.

Use when coordinating multiple enhancers for /enhance command. Runs analyzers in parallel and produces unified report.

Use when improving agent prompts, frontmatter, and tool restrictions.

Use when synthesizing perf findings into evidence-backed recommendations and decisions.

Use when validating task completion before shipping. Runs tests, build, and requirement checks. Returns pass/fail with fix instructions.

Use when analyzing plugin structures, MCP tools, and plugin security patterns.

Use when improving general prompts for structure, examples, and constraints.

Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.

Analyzes your Claude Code conversation history to identify patterns, common mistakes, and opportunities for workflow improvement. Use when user wants to understand usage patterns, optimize workflow, identify automation opportunities, or check if they're following best practices.