awesome-slash

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

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 managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version.

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

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

Use when appending structured perf investigation notes and evidence.

Use when appending structured perf investigation notes and evidence.

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

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

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

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

Use when running controlled perf experiments to validate hypotheses.

Use when running controlled perf experiments to validate hypotheses.

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 validating task completion before shipping. Runs tests, build, and requirement checks. Returns pass/fail with fix instructions.

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

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 managing CHANGELOG entries. Check for undocumented commits, format and apply new entries safely.

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

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.

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.