clonedeps

Clone dependency source repositories into a local workspace for library internals inspection.

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

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 source repositories into an ignored local workspace so agents can inspect implementation details directly. ## Core Features & Use Cases - Curated dependency cloning: Delegates source discovery to the @librarian agent, which recommends only 0-5 high-value repositories with URLs, refs, and rationale instead of dumping every dependency. - Safe, verified git operations: Verifies refs with git ls-remote, prefers pinned tags and shallow HTTPS clones, rejects unsafe URLs, and asks for user approval before cloning. - Persistent local state: Writes a trackable .slim/clonedeps.json manifest, updates .gitignore/.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 matching 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 core 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 your project's core dependency sources. The librarian agent recommends a small set of high-value repositories with URLs and refs, the plan is verified with git ls-remote, and approved repos are cloned read-only under .slim/clonedeps/repos/.

How to debug library internals when docs are not enough?▼

Clone the library's source repository locally and read the implementation directly. This Skill pins the correct version tag, performs a shallow clone, and registers the path in AGENTS.md so agents can inspect the actual code behind the behavior.

Are cloned dependency repositories committed to git?▼

No. Only the cloned repository contents under .slim/clonedeps/repos/ are added to .gitignore via a managed marker block. The small .slim/clonedeps.json manifest is intentionally trackable project metadata that can be committed.

Does it clone every dependency in my project?▼

No. It deliberately avoids dependency dumps and clones at most 3-5 core dependencies such as central frameworks, SDKs, ORMs, or runtime APIs. Tiny utilities, transitive dependencies, and dev-only tools are excluded unless directly relevant.

What happens if a dependency clone fails or the ref is wrong?▼

Refs are verified with git ls-remote before cloning, and failed temporary clones are removed. If some clones succeed before a failure, the manifest still records the successful ones so future inspection is not misleading.

When should I not use dependency source cloning?▼

Do not use it for ordinary API or documentation questions where the librarian agent's knowledge is sufficient. It is meant for cases where reading actual source code is more useful than docs, such as debugging implementation details.