code-intelligence
Skill100 starsChanged 5 days agoMITView on GitHub
Code understanding tool selection. Use when exploring architecture,
4 other projects use a version of this.
Adopted by
Most recently taken up by
- TIKAZI/TIKAZ-Codex-Engineeringtheir own version, first seen Aug 12, 2026
- dachent/skillstheir own version, first seen Aug 9, 2026
- darinh/copilot-toolstheir own version, first seen Jul 22, 2026
- naranor/code-intelligence-skilltheir own version, first seen May 2, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- dachent/skills★ 27same name
- darinh/copilot-tools★ 1same name
- naranor/code-intelligence-skill★ 1same name
- TIKAZI/TIKAZ-Codex-Engineering★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- genesis-external-clientSkill
- build-sessionSkill
- cc-updateSkill
- closing-sessionSkill
- content-publishSkill
- deliverable-builderSkill
- genesis-developmentSkill
- genesis-voiceSkill
- shelveSkill
- spec-sessionSkill
- subsystem-mapSkill
- tasteSkill
- unshelveSkill
- validating-mergesSkill
- voice-masterSkill
- web-researchSkill
- youtube-fetchSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Start cheap, escalate as needed:
- Distinctive: line 33
Serena: Always available. 1-2s init per session.
- Very specific: line 36
codebase_navigate: Always available (Genesis health MCP).
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Code Intelligence Tool Selection
| Need | Tool | Example |
| Package/module overview | codebase_navigate MCP (L0→L1→L2) | "What packages exist?" |
| Symbol definition/signature | Serena find_symbol | "Where is Router defined?" |
| Who calls/references X | Serena find_referencing_symbols | "Who calls _set_output?" |
| File symbol overview | Serena get_symbols_overview | "What's in engine.py?" |
| What breaks if I change X | GitNexus impact | "Blast radius of renaming Router" |
| End-to-end execution flow | GitNexus query | "How does task submission work?" |
| Architecture/clusters | GitNexus context or clusters resource | "What's in the memory package?" |
| String pattern / non-Python | Grep | "Find all TODO comments" |
| File by name | Glob | "Find all *_hook.py files" |
Escalation Path
Start cheap, escalate as needed:
codebase_navigatefor orientation (always available, fast)- Serena for precise symbol work (LSP-powered, Python-only)
- GitNexus for relationships and impact (knowledge graph, needs index)
- Grep/Glob for everything else
Availability
- Serena: Always available. 1-2s init per session.
- GitNexus: Requires index. Check freshness:
.claude/mcp/run-gitnexus status. PostToolUse hook auto-detects staleness after commits. codebase_navigate: Always available (Genesis health MCP).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.