external-repo

Clone external repositories into /tmp/opencode for temporary read-only inspection.

8|1|Updated Mar 9, 2019
One-click install
npx skills add https://github.com/wangl-cc/dotfiles --skill external-repo-wangl-cc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: external-repo
Source: https://github.com/wangl-cc/dotfiles/tree/main/home/dot_config/opencode/skills/external-repo
Command: npx skills add https://github.com/wangl-cc/dotfiles --skill external-repo-wangl-cc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

External Repository Research helps you obtain information from third-party repositories when local code and official docs are not enough, enabling safer, temporary access to external material without modifying it.

Core Features & Use Cases

  • Lightweight first: prefer local code, official docs, and release notes before cloning.
  • Temporary, read-only exploration: clone into /tmp/opencode/<repo-name>/ only when needed, reuse existing checkouts if available.
  • Clear separation from your project: keep external findings isolated from local work and report provenance with file paths and URLs.

Quick Start

Ask the AI to inspect a third-party repository when local code and docs are insufficient and report the URL, checkout path, relevant files, and how it relates to your task.

Frequently Asked Questions about external-repo

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

FAQPage Schema
How do I clone an external repository for temporary read-only reference without modifying my local project?

Cloning an external repository for temporary reference involves checking out third-party code into /tmp/opencode/<repo-name>/, keeping external findings isolated from your local project work and reporting relevant file paths and URLs.

What is the best way to inspect third-party release notes and code when local sources are insufficient?

The best way to inspect third-party release notes and code when local sources fail is by cloning the external repository into a temporary read-only checkout in /tmp/opencode/ to verify the required information.

Does this external repo cloning approach reuse existing checkouts in /tmp/opencode/ to save time?

Yes, this external repo cloning approach reuses existing checkouts in /tmp/opencode/ when available, avoiding redundant downloads while maintaining a temporary read-only reference of the third-party project.

How do I keep external repository findings separated from my own project during research?

To keep external repository findings separated from your project during research, third-party code is cloned into /tmp/opencode/ as temporary read-only material, ensuring local work remains isolated and provenance is reported with file paths and URLs.

When should I use a temporary read-only checkout instead of adding a third-party project as a dependency?

A temporary read-only checkout should be used when you must verify code, readme, or release notes from third-party projects for research without permanently modifying your project or adding formal dependencies.