gitnexus
Skill1 starsChanged 47 days agoMITView on GitHub
Use GitNexus repository graphs to trace symbols, call paths, and change impact before editing unfamiliar or cross-cutting code.
In this repository15 other files it gives its agents.
- skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- build-web-appsSkill
- cavemanSkill
- composioSkill
- context7Skill
- diagnoseSkill
- frontend-testing-debuggingSkill
- grill-meSkill
- security-auditSkill
- superpowersSkill
- tddSkill
- to-prdSkill
- vercel-react-best-practicesSkill
- web-design-guidelinesSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use for unfamiliar repositories, broad refactors, or changes where callers and dependencies are hard to follow.
- Distinctive: line 11
Check that the GitNexus MCP server is connected and the index belongs to the active workspace and current revision.
- Distinctive: line 12
Search for the relevant symbol or execution flow.
- Distinctive: line 13
Read source files to confirm graph results and understand behavior.
- Distinctive: line 14
If the index is missing or stale, report that state.
- Distinctive: line 15
After edits, review the source diff and use the graph again when the affected call graph materially changed.
- Distinctive: line 17
Use GitNexus tools only when Kratos exposes them in the current tool catalog.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Explore with GitNexus
Use for unfamiliar repositories, broad refactors, or changes where callers and dependencies are hard to follow.
- Check that the GitNexus MCP server is connected and the index belongs to the active workspace and current revision.
- Search for the relevant symbol or execution flow. Before editing a shared symbol, inspect its callers and downstream dependencies with impact analysis.
- Read source files to confirm graph results and understand behavior. A graph is navigation evidence, not proof that a change is correct.
- If the index is missing or stale, report that state. Re-index only the active workspace and preserve its instruction files.
- After edits, review the source diff and use the graph again when the affected call graph materially changed.
Use GitNexus tools only when Kratos exposes them in the current tool catalog. Do not run analysis on a different repository or transmit project source to a hosted service.
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.