Claude Skills by avifenesh

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

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

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

Use when reviewing SKILL.md files for structure and trigger quality.

Research any topic online and create learning guides. Use when user asks to 'learn about', 'research topic', 'create learning guide', 'build knowledge base', or 'study subject'.

Use when discovering and prioritizing tasks from configured sources. Handles GitHub, GitLab, local files, and custom sources.

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

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 generating performance hypotheses backed by git history and code evidence.

Use when running controlled perf experiments to validate hypotheses.

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.

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

Use when preparing releases, validating cross-platform compatibility, or updating installation infrastructure. Meta-skill for maintaining awesome-slash's 3-platform architecture.

Use when user asks to 'lint agent configs', 'validate skills', 'check CLAUDE.md', 'validate hooks', 'lint MCP'. Validates agent configuration files against 100 rules.

Use when user wants to Clean AI slop from code. Use for cleanup, remove debug statements, find ghost code, repo hygiene.

Use when user wants to 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 improving agent prompts, frontmatter, and tool restrictions.

Use when improving CLAUDE.md or AGENTS.md project memory files.

Use when checking cross-file consistency: tools vs frontmatter, agent references, duplicate rules, contradictions.

Use when improving documentation structure, accuracy, and RAG readiness.

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