rad-repo

Registers and manages git repositories and repo-groups in a cross-repo registry.

Updated May 24, 2026
One-click install
npx skills add https://github.com/MetalHexx/rad-orc-marketplace --skill rad-repo-metalhexx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rad-repo
Source: https://github.com/MetalHexx/rad-orc-marketplace/tree/main/claude-plugin/skills/rad-repo
Command: npx skills add https://github.com/MetalHexx/rad-orc-marketplace --skill rad-repo-metalhexx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? An AI agent's view is limited to its current working directory, but real work often spans multiple repositories. This Skill maintains a registry of repositories and repo-groups so the agent knows where code lives, what each repo is for, and which repos belong together. ## Core Features & Use Cases - Repo Registration: Register repositories with a slug, remote, default branch, and a required description, resolving worktrees and subdirectories to the durable main clone. - Repo-Groups: Group related repositories under a named scoping unit with a description, so work can be focused on a relevant domain. - Local Binding: Bind registered repos to per-machine local clone paths, keeping team-shared identity separate from machine-specific paths. - Use Case: A feature touches a backend API and a frontend app. Register both repos, group them, and the agent can scope and plan work across both instead of treating the current folder as the whole system. ## Quick Start Ask the agent to register the current repository and describe what it is for so it can be included in cross-repo work.

Frequently Asked Questions about rad-repo

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

FAQPage Schema
How do I register a git repository for cross-repo work?▼

Run repo add with the absolute path and a required description of what the repo is and why an agent would look there. Use the dry-run flag first to preview the resolved main clone, derived slug, and remote before writing anything to the registry.

What is a repo-group and when should I create one?▼

A repo-group is a named list of repo slugs with a required description that scopes work to a domain. Create one when a recurring set of repositories is worked on together, so tasks can reference the group instead of enumerating repos.

Can I register a git worktree or subdirectory as a repo?▼

No, registration always resolves to the repository's durable main clone. If you point the CLI at a worktree or subdirectory, it detects this and registers the main clone path instead, since worktrees are transient.

Why does a repo show as unbound after pulling the shared registry?▼

A repo is unbound when its identity exists in the shared registry file but has no local path on your machine, which is normal for teammates. Run repo bind with the slug and your local clone path to resolve it.

What are the limitations on repo slugs in the registry?▼

Slugs must be lowercase-kebab, unique across both repos and repo-groups, and immutable once registered. To change a slug you must remove the repo and re-add it, so confirm the slug during registration.