repo-map
Skill2 starsChanged 4 months agoMITView on GitHub
Generates or updates a repository's CONTEXT PACK (loadable skill .claude/skills/<prefijo>-<repo>) — architecture, core mechanisms, dependencies and pitfalls with file:line evidence — and seeds its assertions. Use when asked to "map a repo", "generate the repo's context", when /spec-create detects a repo without a pack or with a stale pack, or after /repo-add.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- ychampion/ystacktheir own version, first seen Nov 15, 2026
- ejboy/agent-scriptstheir own version, first seen Nov 13, 2026
- jocarrd/crux-agentstheir own version, first seen Nov 8, 2026
- idaibin/skillstheir own version, first seen Nov 8, 2026
- Tcuzzo/backs-aios-skillstheir own version, first seen Nov 3, 2026
- marinvch/Cortextheir own version, first seen Nov 1, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- AnastasiyaW/claude-code-config★ 214same name
- AnastasiyaW/codex-claude-code-config★ 214same name
- ejboy/agent-scripts★ 118same name
- idaibin/skills★ 6same name
- yeaight7/agent-powerups★ 6same name
- jocarrd/crux-agents★ 4same name
- ychampion/ystack★ 4same name
- Tcuzzo/backs-aios-skills★ 2same name
- David-Florian2013/Stop-trusting-made-it-faster-here-is-5-best-skills-for-Claude-★ 1same name
- hanzhangzzz/agent-skills-zh★ 1same name
3 more not listed
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 repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- as-is-learnSkill
- as-isSkill
- as-is-syncSkill
- clarifySkill
- consistencySkill
- context-reportSkill
- convergeSkill
- harness-initSkill
- implement-taskSkill
- orchestrateSkill
- repo-addSkill
- spec-createSkill
- spec-reviewSkill
- system-mapSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 44
Run scripts/freshness.sh check <pack> — it must come out current.
- Distinctive: line 45
If while verifying you detect an INCONSISTENCY (the code contradicts the registry, an ADR or an existing pack): STOP AND ASK the human.
- Distinctive: line 47
Do not normalize it silently.
- Very specific: line 50
Update the mapa-sistemas index if the context state changed (or request /system-map if the system pack does not exist).
“Common” is measured: kept by at least 6 in 10 of the 12 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
Generate the context pack for repo $ARGUMENTS as a loadable skill:
.claude/skills/$(pack_name_for_repo <repo>)/SKILL.md (name =
<pack_prefix>-<repo>, or the registry's pack field). The goal: any
agent that receives a requirement about this application loads the pack
and works with the correct mental model without rereading the repo.
1. Inputs (from cheapest to most expensive)
- Registry (repos.yaml): role, domain, vcs; current seal with
. scripts/repo-lib.sh && stamp_of_repo <repo>. - As-is facts:
knowledge/as-is/<repo>/{modules,api-surface}.md(regenerate if the seal does not match). - codebase-memory MCP graph if indexed (get_architecture, search_graph, trace_path). If it does not respond, continue without it and declare it in "What I DON'T know".
- Targeted reading of the code: entrypoint, wiring, routes, data layer, external clients. Read what is needed to back each claim.
2. Write the pack
- Template:
templates/pack-repo.md(replace ALL{{...}}and<...>placeholders; frontmatter withgenerado_desde: <repo>: <sello>andverificado:with today's date). - The frontmatter DESCRIPTION is the load trigger: name it with the application, its topics and typical questions.
- Hard rules: without
file:lineevidence a claim does not enter the body (it goes to "What I DON'T know"); the "Pitfalls" and "What I DON'T know" sections are never left empty (if there are no pitfalls yet, say which mistake would be easy to make); budget ~150 lines — detail overflows intoreferences/inside the pack's folder. - Secrets: FORBIDDEN to copy tokens, URLs with credentials or customer data into the pack.
3. Assertions and verification
- Seed/update
scripts/assertions.d/<sistema>.shwith 3+ assertions from the pack's most important claims (format per that folder's README) and runscripts/assertions.sh <sistema>— it must end up green. - Run
scripts/freshness.sh check <pack>— it must come out current. - If while verifying you detect an INCONSISTENCY (the code contradicts the registry, an ADR or an existing pack): STOP AND ASK the human. Do not normalize it silently.
4. Closure
- Update the
mapa-sistemasindex if the context state changed (or request /system-map if the system pack does not exist). - Commit:
docs(packs): pack <pack> @<sello>. - Final summary: mental model in 3 lines + pitfalls + what was left out.
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.

