add-repo
Skill0 starsChanged 4 months agoMITView on GitHub
Register a git checkout into this Atlas instance's repo registry (REPOS.md) so /mediate, /snapshot, and cross-repo work know about it. Use when the user says "/add-repo <path>", "register this repo", or "add <path> to the repos Atlas knows about". Takes a path to a git checkout (defaults to the current directory).
2 other projects use a version of this.
Adopted by
Most recently taken up by
- MostAshraf/ai-sdlc-harnesstheir own version, first seen Nov 15, 2026
- cTuningLabs/cmetatheir own version, first seen Nov 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- MostAshraf/ai-sdlc-harness★ 20same name
- cTuningLabs/cmeta★ 9same 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 repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- fleet/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/atlas.mdcCursor rule
- atlas-setupSkill
- councilSkill
- mediateSkill
- onboardSkill
- optimizeSkill
- registry-syncSkill
- researchSkill
- snapshotSkill
- sync-repo-knowledgeSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Add a git checkout to REPOS.md, the registry of repos this instance governs.
- Very specific: line 22
Write the row: If REPOS.md is missing, create it with the header + table from the template.
- Distinctive: line 23
If a row already exists for this toplevel path or remote, update it.
- Very specific: line 25
Privacy check (public instance): If this Atlas instance is a public repo and the path is a sensitive internal location, do not commit it …
- Very specific: line 28
Sync knowledge: Run the /sync-repo-knowledge procedure on the toplevel path to populate wiki/topics/<name>.md with a knowledge page …
- Distinctive: line 31
Commit only if asked, and keep the message clear (no agent trailer).
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
/add-repo <path> - register a repo into the Atlas hub
Add a git checkout to REPOS.md, the registry of repos this instance governs. Idempotent: if the
repo is already listed, update its row instead of duplicating.
Steps
- Resolve the path from the argument (default: current directory if none given). Confirm it is a
git checkout:
git -C <path> rev-parse --is-inside-work-tree. If not, report and stop. - Gather metadata (run from
<path>):toplevel=git -C <path> rev-parse --show-toplevel(use as the canonical path).name= basename oftoplevel. This is canonical: the REPOS row, the wiki page filename, and the Home link must all use this exact name. Do NOT substitute the package or remote name unless the user explicitly asks; if they do, use that one name consistently in all three places.remote=git -C <path> remote get-url origin(uselocal-onlyif there is no remote).default_branch=git -C <path> symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null(fallback: the current branch fromgit -C <path> branch --show-current).role/notes= ask the user briefly, or infer from the repo README first line.
- Write the row. If
REPOS.mdis missing, create it with the header + table from the template. If a row already exists for this toplevel path or remote, update it; otherwise append a new row. Keep the table columns: Name, Path, Remote, Default branch, Role / notes. - Privacy check (public instance). If this Atlas instance is a public repo and the path is a
sensitive internal location, do not commit it without the user's ok: offer to record it in a
gitignored
REPOS.local.mdinstead, or store only the remote + a relative name. - Sync knowledge. Run the
/sync-repo-knowledgeprocedure on the toplevel path to populatewiki/topics/<name>.mdwith a knowledge page (purpose, structure, state, recent activity). - Report what was added or updated (name, path, remote, branch) and that knowledge was synced. Commit only if asked, and keep the message clear (no agent trailer).
Notes
- This only registers the repo; it does not clone, modify, or take ownership of it.
- Ownership of areas within a repo is tracked separately in
OWNERSHIP.mdand gated by/mediate.
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.

