repo-intel
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.
Best use case
repo-intel is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using repo-intel should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/repo-intel/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How repo-intel Compares
| Feature / Agent | repo-intel | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Repo Intel Skill
Unified static analysis - git history intelligence, AST symbol mapping, and project metadata via agent-analyzer.
## Parse Arguments
```javascript
const args = '$ARGUMENTS'.split(' ').filter(Boolean);
const action = args.find(a => !a.startsWith('--')) || 'status';
const force = args.includes('--force');
```
## Primary Responsibilities
1. **Initialize** on demand (`/repo-intel init`)
2. **Update** incrementally (`/repo-intel update`)
3. **Query** git history data (`/repo-intel query hotspots`)
4. **Check status** and staleness (`/repo-intel status`)
5. **Validate output** with the map-validator agent
## Core Data Contract
Repo intel data is stored in the platform state directory:
- Claude Code: `.claude/repo-intel.json`, `.claude/repo-map.json`
- OpenCode: `.opencode/repo-intel.json`, `.opencode/repo-map.json`
- Codex CLI: `.codex/repo-intel.json`, `.codex/repo-map.json`
## Behavior Rules
- **Never** install dependencies without explicit user consent
- **Always** validate output with `map-validator` after init/update
- **Prefer** incremental update unless data is stale or history rewritten
## When to Suggest Repo Intel
If 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
```
## Staleness Signals
- Data commit not found (rebased)
- Branch changed
- Git hooks marked stale
- Commits behind HEAD
## Output Expectations
Keep outputs concise:
- **init/update**: file count, symbol count, commit, warnings
- **query**: formatted query results
- **status**: staleness, commits behind, last updatedRelated Skills
debate
Structured AI debate templates and synthesis. Use when orchestrating multi-round debates between AI tools, 'debate topic', 'argue about', 'stress test idea', 'devil advocate'.
perf-benchmarker
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.
learn
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'.
perf-analyzer
Use when synthesizing perf findings into evidence-backed recommendations and decisions.
drift-analysis
Use 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.
discover-tasks
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.
perf-theory-gatherer
Use when generating performance hypotheses backed by git history and code evidence.
enhance-cross-file
Use when checking cross-file consistency: tools vs frontmatter, agent references, duplicate rules, contradictions.
enhance-hooks
Use when reviewing hooks for safety, timeouts, and correct frontmatter.
enhance-prompts
Use when improving general prompts for structure, examples, and constraints.
validate-delivery
Use when user asks to "validate delivery", "check readiness", or "verify completion". Runs tests, build, and requirement checks with pass/fail instructions.
deslop
Use when user wants to clean AI slop from code. Use for cleanup, remove debug statements, find ghost code, repo hygiene.