Clonedeps Skill

You help users make a small set of important dependency source repositories locally readable to OpenCode.

This is a workflow skill, not a command wrapper. Do not use a helper script for dependency detection, ref validation, cloning, status, or cleanup. The orchestrator and @explorer do the repo-specific thinking; the orchestrator performs the approved filesystem/git operations directly.

Workflow

Step 1: Check Existing State

First check whether .slim/clonedeps.json exists.

If it exists:

1. Read it before asking explorer for a new plan.
2. Check whether each listed path exists under .slim/clonedeps/repos/.
3. Reuse existing cloned repos when they already satisfy the user's task.
4. Only ask explorer for new recommendations if the existing manifest is missing, stale, or insufficient for the current task.

Do not rescan/re-plan from scratch when the manifest already has useful entries.

Step 2: Ask Explorer for the Clone Plan

Delegate dependency discovery and source resolution to @explorer.

Use this prompt:

Understand this project first, then recommend remote source repos that would
help a developer work on it.

Read enough of the current repo to understand:
- what the project does
- its main architecture
- the important integration points
- what external systems or libraries it depends on in practice

Think like a developer trying to debug or extend this project.

Which remote repositories, if cloned locally, would actually help understand the
codebase or solve likely implementation/debugging tasks?

Do not make a dependency dump. Most dependencies are not worth cloning.
Recommend a repo only when its source code would be more useful than docs or the
current repo alone.

For each recommendation, include:
- repo name
- repo URL
- suggested ref/tag/commit if known
- why cloning this source would help
- when it would be useful
- caveats