mcpbeat

Git Repo Manager

coinbase/git.repo-manager

Instructions 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.

393 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
491
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/coinbase/cds --skill git.repo-manager

What it tells the agent to use

found in the instruction text
Bash runs shell commands — read the instruction before connecting

The instruction itself

3 sections, as written by the author

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

How to use it

Copy the folder

Take coinbase/git.repo-manager from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.