repo-onboarding

Onboard repositories into Codex Workspace with runtime metadata and agent-tooling conventions.

2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/RichardGeorgeDavis/Codex-Workspace --skill repo-onboarding-richardgeorgedavis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-onboarding
Source: https://github.com/RichardGeorgeDavis/Codex-Workspace/tree/main/shared/skills/repo-onboarding
Command: npx skills add https://github.com/RichardGeorgeDavis/Codex-Workspace --skill repo-onboarding-richardgeorgedavis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboard a repository into Codex Workspace with runtime metadata, AGENTS guidance, and agent-tooling conventions to streamline setup and governance.

Core Features & Use Cases

  • Conservative repository classification from files to determine workspace posture.
  • Ensure README.md exists, add a repo-local cover, and populate runtime manifests where needed.
  • Provide optional scaffolding for Codex-visible capabilities (.codex/skills/), agent tooling skills (.agents/skills/), and multi-tool hints (.workspace/agent-stack.json).

Quick Start

Run tools/scripts/bootstrap-repo.sh to bootstrap the new repo and follow the AGENTS guidance to complete onboarding.

Frequently Asked Questions about repo-onboarding

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

FAQPage Schema
How do I onboard a repository into Codex Workspace with agent tooling?

Onboard a repository by running the bootstrap script to classify files, enforce a README, add a repo cover block, and scaffold runtime manifests like .workspace/agent-stack.json for automation. This establishes the required metadata and agent conventions.

What runtime metadata do I need to set up a workspace for automation?

Workspace automation requires runtime manifests such as .workspace/agent-stack.json for multi-tool hints, optional .codex/skills/ for capabilities, and .agents/skills/ scaffolding. You also need an AGENTS.md file when agent guidance is necessary.

How does conservative file-based repository classification work for onboarding?

Conservative repository classification analyzes existing files to determine workspace posture, ensuring only documented structures are recognized. This prevents misconfigurations by relying on actual file presence rather than assumptions during the onboarding process.

Can I add existing repos under repos/ without manually writing all the documentation?

Adding existing repos triggers automated documentation setup that checks for README.md existence and adds a repo-local cover block. It also scaffolds optional Codex-visible capabilities, reducing manual documentation overhead.

What is the best way to scaffold agent-stack.json and AGENTS.md for a new repo?

The best way to scaffold agent-stack.json and AGENTS.md is running the bootstrap script, which conservatively classifies the repository and generates the required workspace agent hints and guidance files automatically.

Do I need dependencies installed to bootstrap repository onboarding metadata?

No dependencies are required to bootstrap repository onboarding metadata. The process runs standalone to classify files, enforce documentation rules, and generate runtime manifests without external packages.