Claude Skills

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

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

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

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

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

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 synthesizing perf findings into evidence-backed recommendations and decisions.

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

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

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 mapping code paths, entrypoints, and likely hot files before profiling.

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 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 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 coordinating multiple enhancers for /enhance command. Runs analyzers in parallel and produces unified report.

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