Claude Skills

Use when analyzing doc issues after code changes. Check for outdated references, stale examples, and missing updates.

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

Sync documentation with code. Use when user asks to update docs, check docs, fix stale documentation, update changelog, or after code changes.

Use when generating performance hypotheses backed by git history and code evidence.

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

Use when user asks to \"deep review the code\", \"thorough code review\", \"multi-pass review\", or when orchestrating Phase 9 review loop. Provides review pass definitions (code quality, security, performance, test coverage, specialists), signal detection patterns, and iteration algorithms.

Use when updating documentation related to recent code changes. Finds related docs, updates CHANGELOG, and delegates simple fixes to haiku.

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

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

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

Use when mapping code paths, entrypoints, and likely hot files before profiling.

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

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

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

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 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 generating the unified enhancement report from aggregated findings. Called by orchestrator after all enhancers complete.

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

Generate multiple diverse solutions in parallel and select the best. Use for architecture decisions, code generation with multiple valid approaches, or creative tasks where exploring alternatives improves quality.