dev-env-setup

Clone repositories and generate CLADE context files for multi-repo environments.

7|15|Updated Jan 23, 2026

Search Tags:#automation #setup #dev environment #multi-repo #clones #preset configuration #claude context

Ready to run

npx skills add https://github.com/openshift-eng/edge-tooling --skill dev-env-setup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-env-setup
Source: https://github.com/openshift-eng/edge-tooling/tree/main/multi-repo-development/.claude/skills/dev-env-setup
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill dev-env-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It saves developers from manually cloning, configuring, and wiring together many repositories into a ready-to-work multi-repo CLADE workflow.

Core Features & Use Cases

Preset or custom environment setup: Initialize an environment from a team-maintained preset or build it from scratch based on your requirements.
Repo cloning and CLAUDE context seeding: Clone all repos defined in dev-env.yaml and create or copy repo CLAUDE.md context files when appropriate, without overwriting native CLAUDE.md.
Root CLAUDE.md repo table generation: Automatically refresh the root CLAUDE.md table so the environment is discoverable and task-ready.
Collaborative context generation: Optionally explore repositories and generate targeted context drafts for repos that lack native CLAUDE.md.

Quick Start

Ask Claude: “Run dev-env-setup with setup custom and help me build my dev environment for my multi-repo project.”

Frequently Asked Questions about dev-env-setup

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

FAQPage Schema

How do I set up a multi-repo development environment without manually cloning each repository?▼

Multi-repo development environment setup is handled by cloning repositories defined in a dev-env.yaml configuration file and automatically preparing the required context files for an integrated workflow.

Can I use a preset configuration to onboard a multi-repo project instead of building from scratch?▼

Preset configuration onboarding is fully supported, allowing you to initialize a multi-repo environment from a team-maintained template by copying the preset dev-env.yaml and settings files to start quickly.

How does the setup process handle CLAUDE.md context files for repositories that already have them?▼

Repository CLAUDE.md context files are distributed during setup without overwriting any native CLAUDE.md files, ensuring existing context is preserved while seeding context for repos that lack it.

What is the best way to generate a root context file that lists all my cloned repositories?▼

Root CLAUDE.md repo table generation automatically refreshes the root context file during environment initialization, making all cloned repositories discoverable and task-ready.

How do I create context drafts for repositories in my dev environment that lack native context files?▼

Collaborative context generation optionally explores repositories lacking native CLAUDE.md files, creating targeted context drafts to provide necessary project background for the workflow.