bootstrap-development-system

Audit and prepare Git repositories for a canonical agent-driven Development System.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/AO-HyS/aohys.com --skill bootstrap-development-system-ao-hys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bootstrap-development-system
Source: https://github.com/AO-HyS/aohys.com/tree/main/.agents/skills/bootstrap-development-system
Command: npx skills add https://github.com/AO-HyS/aohys.com --skill bootstrap-development-system-ao-hys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Onboarding a repository to an agent-driven development workflow requires consistent lifecycle routing, phase commands, and architecture guidance, and doing this by hand risks drift, foreign-product residue, and unmanaged file changes. ## Core Features & Use Cases - Read-only repository audit: Runs a fingerprint-bound audit that reports per-harness readiness (Codex, T3 Code), detected stack and commands, and concrete gaps such as missing review, validation, QA, or preview commands. - Idempotent initialization and normalization: Applies the managed adapter contract by initializing unmanaged repositories or normalizing existing ones, writing only to .development-system/repository.json and .codex/development-system/repository.md. - Side-effect verification: Snapshots pre-existing dirty paths, detects unexpected changed paths and external side effects, and warns on unhealthy global installations or contract version mismatches. - Use Case: When creating a new repository or onboarding an existing one to Codex or T3 Code, run the audit to confirm lifecycle routing and phase commands are structurally ready before authorizing any preparation. ## Quick Start Ask the agent to audit this repository for Development System readiness and report any gaps before applying the adapter.

Frequently Asked Questions about bootstrap-development-system

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

FAQPage Schema
How do I onboard a repository to an agent-driven development workflow?▼

Run the bootstrap script in audit mode first to inspect readiness, then rerun with --apply after authorizing preparation. The script initializes unmanaged repositories or normalizes existing adapters, writing only to the managed Development System files.

How do I check if a repository is ready for Codex or T3 Code?▼

Run the audit command with --json to get per-harness readiness status. A repository is prepared only when lifecycle routing, phase commands, and required review, validation, QA, and preview commands are structurally present.

Which files does the Development System bootstrap modify?▼

It writes only .development-system/repository.json and .codex/development-system/repository.md, and may remove the retired .factory/development-system/repository.md adapter. Any change outside these managed paths is reported as an unexpected side effect.

Why does the bootstrap report needs-preparation after running?▼

The status means the audit found concrete gaps such as missing review, validation, QA, or preview commands, inert skills, or foreign-product residue. Add real product commands and re-run --apply; the skill never fabricates commands to force readiness.

Can the bootstrap skill deploy or configure hosting for my repository?▼

No. It explicitly does not install a release train, configure hosting, deploy, commit, push, or open pull requests. Those actions require separate authorization and belong to other workflows such as bootstrap-release-train.