git.repo-manager
DevelopmentInstructions to manage a local cache of GitHub repositories. This would typically done in cases where the user want to perform research/analysis on a repository. Invoke whenever you need to clone a repo that isn't present locally, bring an existing clone up to date, or remove a repo from the cache. This skill handles only the mechanical filesystem/git operations — not research, analysis, or anything about the repo's contents.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/coinbase/cds/blob/HEAD/.claude/skills/git.repo-manager/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/git-repo-manager, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Manages a local repository cache at temp/repo-cache/. Use these patterns for repo lifecycle operations.
Ensure a repo is available and up to date
-
Check whether the repo directory already exists:
test -d temp/repo-cache/<name> && echo "exists" || echo "missing" -
If missing — clone a shallow copy of the default branch:
git clone --depth 1 <repo-url> temp/repo-cache/<name> --quiet -
If already present — pull the latest commits:
cd temp/repo-cache/<name> && git pull --quiet
Clean up a repo
Remove a cached repo when it's no longer needed or when explicitly asked:
rm -rf temp/repo-cache/<name>
Rules
- Always use
temp/repo-cache/as the cache root — never clone repos to other locations - Always clone with
--depth 1(shallow) to minimize disk usage and clone time - Never clone more than the single repo you need for the current task