repo-cache

Cache and reuse remote Git repositories locally via a checkout script.

37|7|Updated Apr 8, 2026

Search Tags:#automation #git #repository #cache #checkout #local-cache

Ready to run

npx skills add https://github.com/archibate/dotfiles-claude --skill repo-cache

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repo-cache
Source: https://github.com/archibate/dotfiles-claude/tree/main/skills/repo-cache
Command: npx skills add https://github.com/archibate/dotfiles-claude --skill repo-cache

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Caches and reuses local checkouts of remote Git repositories to speed up code exploration and reduce repeated clones.

Core Features & Use Cases

Deterministic local cache location at ~/.cache/checkouts/<host>/<org>/<repo> for reliable path references.
Throttled updates with optional force refresh to keep checkouts fresh without excessive network usage.
Path-only output and integration-friendly behavior to plug into tooling and automation.

Quick Start

Run scripts/checkout.sh <repo> to create or reuse a cached local checkout and print its path.

Frequently Asked Questions about repo-cache

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I cache a remote Git repository locally to speed up code exploration?▼

To cache a remote Git repository locally, run the provided checkout script with the repository URL to create or reuse a deterministic local checkout, speeding up code exploration without re-downloading.

What is the best way to avoid re-downloading GitHub or GitLab repositories for repeated codebase searches?▼

The best way to avoid re-downloading repositories is using a local checkout cache, which stores remote Git repositories at a deterministic local path so you can search across the codebase instantly without network delays.

Can I force refresh a local Git checkout when the upstream repository updates?▼

Yes, you can force refresh a local Git checkout. The caching mechanism supports throttled updates with an optional force refresh to keep your local checkouts fresh without excessive network usage.

Does the local Git checkout cache work with Bitbucket and GitLab forks?▼

Yes, the local Git checkout cache works with Bitbucket and GitLab forks. It applies when you need to clone or inspect code from GitHub, GitLab, or Bitbucket and study forks locally without re-cloning.

How do I integrate a cached repository path into my existing automation tooling?▼

You can integrate a cached repository path into automation tooling because the checkout script provides path-only output and integration-friendly behavior, returning a deterministic local cache location for reliable references.