Files
repoctl/.claude/skills/repository-bootstrap/SKILL.md
T
Alexander BaranovandClaude Opus 5 79ea43d5bf fix(skills): sync the distributed adoption skill and pin it to the repo copy
`init` writes .claude/skills/*/SKILL.md into every new repository from the
constants in skills_content, so each skill exists twice: once as the copy
this repository uses, once as the copy it ships. Editing one and not the
other went unnoticed by validate and by every test.

It had already happened. The shipped repository-adoption skill still told
its reader to use `--strategy normalize --recipe documents-to-content-root`
-- an operation the CLI does not offer and CLAUDE.md forbids claiming --
and said nothing about the owner requirement or acknowledged findings.
Every repository bootstrapped since would have received that copy.

Sync both, and add a test that compares each shipped skill against the
checked-in one so the next divergence fails instead of shipping.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-25 18:11:13 +03:00

1.4 KiB

name, description
name description
repository-bootstrap Bootstrap a new repository into Repository Stewardship using repoctl init. Use when creating a new repository or scaffolding ops/contract.yaml, kdb/kdb.yaml and agent entrypoints from scratch.

repository-bootstrap

Thin wrapper around repoctl init. Do not reimplement classification, template rendering or validation here - call the CLI and explain its output.

Procedure

  1. Collect the missing decisions from the user: repository type (infrastructure-config | service-config | software | project), metadata.name, title, owners, lifecycle. All of these are refused rather than guessed: name must match ^[a-z][a-z0-9]*(?:[.-][a-z0-9]+)*$, owners must be non-empty, and lifecycle must be one of the schema's values. If the target directory already holds ops/contract.yaml or the other generated paths, this is an existing repository: use repository-adoption, not init.
  2. Run repoctl init --repo <path> --answers <answers-file> --output json to obtain a BootstrapPlan (this performs no writes).
  3. Show the user the planned files and the planHash.
  4. Only after explicit approval, run repoctl init --repo <path> --apply --plan <plan-file> --approve <planHash>.
  5. Report the resulting repoctl validate --repo <path> findings.

Never invent files outside the plan and never skip the approval step.