Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
coinbase avatar

Git.Repo Manager

  • 10 installs
  • 493 repo stars
  • Updated July 31, 2026
  • coinbase/cds

Manages a local cache of GitHub repositories for research: cloning shallow copies, pulling updates, and removing clones under temp/repo-cache.

About

Handles the mechanical git operations for a local repo cache at temp/repo-cache, cloning shallow copies, pulling latest commits, and cleaning up. A developer uses it when a repo needs to be present locally for analysis.

  • Always shallow-clones into temp/repo-cache
  • Clones only the single repo needed for the task

Git.Repo Manager by the numbers

  • 10 all-time installs (skills.sh)
  • Ranked #431 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/coinbase/cds --skill git.repo-manager

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs10
repo stars493
Last updatedJuly 31, 2026
Repositorycoinbase/cds

What it does

Manages a local cache of GitHub repositories for research: cloning shallow copies, pulling updates, and removing clones under temp/repo-cache.

Files

SKILL.mdMarkdownGitHub ↗

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

1. Check whether the repo directory already exists:

   test -d temp/repo-cache/<name> && echo "exists" || echo "missing"

2. If missing — clone a shallow copy of the default branch:

   git clone --depth 1 <repo-url> temp/repo-cache/<name> --quiet

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

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.