| name | repo-cache |
| description | Clone or reuse a cached local checkout of a remote git repo (GitHub/GitLab/Bitbucket). Use when the user gives a repo URL or `owner/repo` identifier (e.g. "facebook/react"), says "clone this repo" / "read the source", or needs to browse a remote codebase.
|
Use this skill when the user points you to a remote git repository (GitHub/GitLab/Bitbucket URLs, git@..., or owner/repo shorthand).
The goal is to keep a reusable local checkout that is:
- stable (predictable path)
- up to date (periodic fetch + fast-forward when safe)
- efficient (partial clone with
--filter=blob:none, no repeated full clones)
Cache location
Repositories are stored at:
~/.cache/checkouts/<host>/<org>/<repo>
Example:
github.com/facebook/react → ~/.cache/checkouts/github.com/facebook/react
Command
scripts/checkout.sh <repo> --path-only
Examples:
scripts/checkout.sh facebook/react --path-only
scripts/checkout.sh github.com/facebook/react --path-only
scripts/checkout.sh https://github.com/facebook/react --path-only
The script will:
- Parse the repo reference into host/org/repo.
- Clone if missing.
- Reuse existing checkout if present.
- Fetch from
origin when stale (default interval: 300s).
- Attempt a fast-forward merge if the checkout is clean and has an upstream.
Update strategy
- Default behavior is throttled refresh (every 5 minutes) to avoid unnecessary network calls.
- Force immediate refresh with:
scripts/checkout.sh <repo> --force-update --path-only
Recommended workflow
- Resolve repository path via
checkout.sh --path-only.
- Use that path for searching, reading, and analysis.
- On later references to the same repo, call
checkout.sh again; it will find and update the cached checkout.
If edits are needed
Prefer not to edit directly in the shared cache. Create a separate worktree or copy from the cached checkout for task-specific modifications.
Notes
owner/repo defaults to github.com.
