add-project

Registers an existing git repository in registry.yaml for team-lead coordination.

Updated May 12, 2026
One-click install
npx skills add https://github.com/fryanpan/ai-team-lead --skill add-project-fryanpan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: add-project
Source: https://github.com/fryanpan/ai-team-lead/tree/main/.claude/skills/add-project
Command: npx skills add https://github.com/fryanpan/ai-team-lead --skill add-project-fryanpan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When running a multi-agent Claude Code setup, the team-lead agent needs to know which project repos exist and where they live. This Skill appends an existing repository to the local registry.yaml file so the team-lead can discover and coordinate with it via claude-hive, without manual YAML editing. ## Core Features & Use Cases - Registry Entry Creation: Gathers the project name, local path, GitHub repo, and Linear team details, then appends a correctly formatted entry to registry.yaml. - Validation & Safety Checks: Verifies the path is a real git repository, checks for duplicate registrations, and warns before overwriting anything. - Git-Safe by Design: registry.yaml is gitignored and never committed, keeping project names and team IDs private. - Use Case: You just cloned an existing repo into ~/dev and want your team-lead agent to manage it. Run /add-project, answer a few prompts, and the project is registered and reachable via claude-hive. ## Quick Start Ask the agent to register the existing repository at ~/dev/my-app with GitHub repo your-org/my-app using the add-project skill.

Frequently Asked Questions about add-project

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

FAQPage Schema
How do I register an existing repo with the team-lead agent?▼

Run the /add-project skill and provide the project name, local path, GitHub repo, and optionally the Linear team. The skill verifies the path is a git repository and appends a formatted entry to registry.yaml.

What is the difference between /add-project and /new-project?▼

/add-project only registers a repo that already exists locally. /new-project scaffolds a brand-new repo with GitHub, Linear, .claude config, and docs, then calls /add-project as its final step.

Why should registry.yaml not be committed to git?▼

registry.yaml contains project names and team IDs that should stay private. It is gitignored and lives only in the main worktree, so the skill explicitly avoids committing it and warns you not to.

What happens if the project is already registered in registry.yaml?▼

The skill reads registry.yaml before appending and checks for an existing entry with the same name. If a duplicate is found, it warns you and stops instead of overwriting.

What if the local path I provide is not a git repository?▼

The skill runs git rev-parse --show-toplevel on the path to verify it resolves to a git repo. If verification fails, it stops and asks you where the repository actually lives.