clonedeps

Clone dependency source repositories into an ignored local workspace for agent inspection.

Updated Jun 16, 2022
One-click install
npx skills add https://github.com/SimonZimmer/dotfiles --skill clonedeps-simonzimmer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clonedeps
Source: https://github.com/SimonZimmer/dotfiles/tree/main/.config/opencode/skills/clonedeps
Command: npx skills add https://github.com/SimonZimmer/dotfiles --skill clonedeps-simonzimmer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging or extending a project often requires reading the actual source code of its dependencies, but library internals are not available locally and docs alone are insufficient. This Skill clones a small set of important dependency repositories into a local, git-ignored workspace so agents can inspect library implementation details directly. ## Core Features & Use Cases - Curated Clone Planning: Delegates dependency discovery to the @librarian agent, which recommends only 0-5 high-value source repositories with URLs, refs, and rationale instead of dumping every dependency. - Safe Manual Git Operations: Verifies refs with git ls-remote, enforces HTTPS-only URLs, prefers pinned tags and shallow clones, and clones into temporary directories before finalizing. - Persistent Local State: Writes a structured .slim/clonedeps.json manifest, updates .gitignore and .ignore marker blocks, and registers a Cloned Dependency Source section in AGENTS.md so future agents know what exists. - Use Case: While debugging unexpected SDK behavior, ask to clone the SDK's source repo; the Skill verifies the correct version tag, clones it read-only under .slim/clonedeps/repos/, and records it for future sessions. ## Quick Start Ask the agent to clone the source repositories of this project's most important dependencies so you can inspect their internals locally.

Frequently Asked Questions about clonedeps

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

FAQPage Schema
How do I clone dependency source code for local inspection?▼

Ask the agent to clone important dependency sources; it delegates discovery to the @librarian agent, verifies refs with git ls-remote, and clones approved repos into .slim/clonedeps/repos/ as read-only copies. A manifest in .slim/clonedeps.json records each clone for reuse.

How are dependencies selected for cloning?▼

The @librarian agent reads the project to understand its architecture and recommends only 0-5 repositories whose source is more useful than documentation. Tiny utilities, transitive dependencies, and dev-only tools are excluded unless directly relevant to the task.

Are cloned dependency repositories tracked by git?▼

No. The .slim/clonedeps/repos/ directory is added to .gitignore via a managed marker block, while .slim/clonedeps.json remains trackable project metadata. An .ignore allowlist keeps the clones readable to the agent.

Can I clone private or SSH-based repositories?▼

By default only HTTPS GitHub/GitLab-style URLs are allowed. SSH URLs, file:// paths, embedded credentials, and private or auth-required repositories are rejected unless the user explicitly approves that case.

What happens if a dependency clone fails partway through?▼

Failed temporary clones are removed, and the manifest still records any successful clones so future inspection is not misled. Existing clones are verified against their approved origin URL before reuse.

When should I not use dependency source cloning?▼

Avoid it for ordinary API or documentation questions where the @librarian agent's knowledge is sufficient. Cloning is intended for debugging implementation details or understanding framework behavior that docs cannot answer.