clonedeps

Clone dependency source repositories into a local ignored workspace.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/forgefabrik/agent-bigbrother --skill clonedeps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clonedeps
Source: https://github.com/forgefabrik/agent-bigbrother/tree/main/.config/opencode/skills/clonedeps
Command: npx skills add https://github.com/forgefabrik/agent-bigbrother --skill clonedeps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you make important dependency source code locally readable so you can inspect internals, debug framework behavior, and understand how external libraries actually work inside a project.

Core Features & Use Cases

  • Selective source mirroring: Clones only the small set of dependency repositories that are most useful for real implementation or debugging work.
  • Safe workflow control: Uses librarian-assisted discovery, manual ref verification, and orchestrator-owned git operations instead of brittle automation.
  • Project integration: Records cloned sources in .slim/clonedeps.json, updates ignore rules, and registers the result in AGENTS.md for future agents.
  • Use case: When a project depends on a framework, SDK, plugin API, or ORM with unclear runtime behavior, this Skill makes the source available locally for inspection.

Quick Start

Use the clonedeps skill to inspect the current project, identify the most useful dependency source repositories, and mirror the approved ones into the local ignored workspace.

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 locally to inspect framework internals?

Cloning dependency source code locally mirrors key external repositories into a workspace, letting you inspect SDK internals and debug framework behavior without relying on docs alone. It selectively mirrors the most useful sources for your project.

What is the best way to make external library source code readable for debugging?

Making external library source code readable requires mirroring approved dependency repositories into a local ignored workspace. It uses librarian-assisted source discovery and manual ref verification to ensure safe, repeatable cloning instead of brittle automation.

Can I use git to selectively mirror only the dependencies I need for my project?

Yes, you can use git to selectively mirror dependencies by identifying the small set of repositories most useful for implementation work. It uses orchestrator-owned git operations to clone only approved sources into your local workspace.

How do I track cloned dependency repositories in my project manifest?

Tracking cloned dependency repositories happens through a manifest file at .slim/clonedeps.json. It records cloned sources there, updates ignore rules to exclude them from version control, and registers the workspace in AGENTS.md for future agents.

Does cloning dependency sources locally clutter my main git repository?

Cloning dependency sources locally does not clutter your main git repository because the skill places sources in an ignored workspace and automatically updates your ignore files. This keeps external source mirrors separate from your project code.

When do I need to clone SDK and plugin source repositories into a local workspace?

You need to clone SDK and plugin source repositories into a local workspace when a project depends on frameworks with unclear runtime behavior and you must inspect the actual implementation code. This makes external API behavior locally readable for debugging.