// 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 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 mapping code paths, entrypoints, and likely hot files before profiling.
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.
| name | repo-intel |
| description | 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. |
| argument-hint | [action] [--force] |
Unified static analysis - git history intelligence, AST symbol mapping, and project metadata via agent-analyzer.
const args = '$ARGUMENTS'.split(' ').filter(Boolean);
const action = args.find(a => !a.startsWith('--')) || 'status';
const force = args.includes('--force');
/repo-intel init)/repo-intel update)/repo-intel query hotspots)/repo-intel status)Repo intel data is stored in the platform state directory:
.claude/repo-intel.json, .claude/repo-map.json.opencode/repo-intel.json, .opencode/repo-map.json.codex/repo-intel.json, .codex/repo-map.jsonmap-validator after init/updateIf a user asks for drift detection, documentation alignment, or repo analysis and repo-intel data is missing:
Repo intel data not found. For better analysis, run:
/repo-intel init
Keep outputs concise: