// Use when mapping code paths, entrypoints, and likely hot files before profiling.
| name | perf-code-paths |
| description | Use when mapping code paths, entrypoints, and likely hot files before profiling. |
| version | 5.1.0 |
Identify likely implementation paths for a performance scenario.
Follow docs/perf-requirements.md as the canonical contract.
keywords: <comma-separated list>
paths:
- file: <path>
symbols: [<symbol1>, <symbol2>]
evidence: <short reason>
Use when user asks to "discover tasks", "find next task", "prioritize issues", "what should I work on", or "list open issues". Discovers and ranks tasks from GitHub, GitLab, local files, and custom sources.
Use when preparing releases, validating cross-platform compatibility, or updating installation infrastructure. Meta-skill for maintaining AgentSys's 3-platform architecture.
Use when user asks to "run repo intel", "generate repo map", "analyze repo", "query hotspots", "check ownership", or "bus factor". Unified static analysis - git history, AST symbols, project metadata.
Use when generating performance hypotheses backed by git history and code evidence.
Structured AI debate templates and synthesis. Use when orchestrating multi-round debates between AI tools, 'debate topic', 'argue about', 'stress test idea', 'devil advocate'.
Use when user wants to clean AI slop from code. Use for cleanup, remove debug statements, find ghost code, repo hygiene.