Repo Intel
- 1 installs
- 931 repo stars
- Updated July 26, 2026
- avifenesh/awesome-slash
repo-intel is a skill that runs unified static analysis over a repository (git history, AST symbols, project metadata) and lets you query hotspots, ownership, and bus factor.
About
This skill performs unified static analysis of a repository, combining git history intelligence, AST symbol mapping, and project metadata. A developer uses it to generate a repo map and query hotspots, code ownership, or bus factor. It initializes and updates incrementally, stores data in the platform state directory, and validates output with a map-validator agent.
- Unified static analysis of git history, AST symbols, and project metadata
- Queries hotspots, ownership, and bus factor from a cached repo map
- Stores intel per platform and validates output with a map-validator agent
Repo Intel by the numbers
- 1 all-time installs (skills.sh)
- Ranked #984 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
repo-intel capabilities & compatibility
- Capabilities
- static analysis · repo mapping · hotspot analysis · code ownership
- Works with
- github
- Use cases
- code review · refactoring · research
What repo-intel says it does
Unified static analysis - git history intelligence, AST symbol mapping, and project metadata via agent-analyzer.
npx skills add https://github.com/avifenesh/awesome-slash --skill repo-intelAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 931 |
| Last updated | July 26, 2026 |
| Repository | avifenesh/awesome-slash ↗ |
What it does
Generate and query a static analysis map of git history, AST symbols, hotspots, and ownership for a repo.
Who is it for?
Developers who need repo-wide intelligence like hotspots, ownership, and bus factor to guide refactoring or reviews.
Skip if: Editing code or running the app; this skill only analyzes and reports on the repository.
When should I use this skill?
You ask to run repo intel, generate a repo map, analyze the repo, query hotspots, check ownership, or bus factor.
What you get
A cached, queryable repo map surfacing hotspots, ownership, and bus-factor risk.
- repo-intel.json
- repo-map.json
- hotspot and ownership queries
By the numbers
- stores repo-intel.json and repo-map.json per platform
Files
Repo Intel Skill
Unified static analysis - git history intelligence, AST symbol mapping, and project metadata via agent-analyzer.
Parse Arguments
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-validatorafter 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 initStaleness 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 updated
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264kFAQ
What does repo-intel analyze?
Git history intelligence, AST symbols, and project metadata, combined into a unified repo map.
How is the map kept fresh?
It prefers incremental updates unless data is stale or history was rewritten, and it detects staleness signals like rebases and branch changes.