Menu
Use when appending structured perf investigation notes and evidence.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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 mapping code paths, entrypoints, and likely hot files before profiling.
Use when generating performance hypotheses backed by git history and code evidence.
Cross-tool AI consultation. Use when user asks to 'consult gemini', 'ask codex', 'get second opinion', 'cross-check with claude', 'consult another AI', 'ask opencode', 'copilot opinion', or wants a second opinion from a different AI tool.
| name | perf-investigation-logger |
| description | Use when appending structured perf investigation notes and evidence. |
| version | 5.1.0 |
Append structured investigation notes to {state-dir}/perf/investigations/<id>.md.
Follow docs/perf-requirements.md as the canonical contract.
## <Phase Name> - <YYYY-MM-DD>
**User Quote:** "<exact quote>"
**Summary**
- ...
**Evidence**
- Command: `...`
- File: `path:line`
**Decision**
- ...
AI_STATE_DIR for state path (default .claude).