`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>
1.7 KiB
1.7 KiB
name, description
| name | description |
|---|---|
| repository-adoption | Assess and adopt an existing repository into Repository Stewardship using repoctl adopt. Use when connecting an existing, non-templated repository without moving its domain content. |
repository-adoption
Thin wrapper around repoctl adopt. The canonical procedure is
docs/adoption-runbook.md; this skill only collects missing decisions, calls the CLI
with machine output, and explains findings. It must not duplicate the runbook logic.
Procedure
- Run
repoctl adopt --repo <path> --mode assess --output json(read-only). - Present the classification, detected content roots, and any
questionsthat need owner confirmation. - Run
repoctl adopt --repo <path> --mode plan --owner <owner> --output jsononce open questions are resolved. This is still read-only and returns anAdoptionPlanwith aplanHash.planrefuses without a confirmed owner, and refuses whileassessleft an error-severity finding; an owner who accepts one lists it underacknowledgedFindings(with areason) in the--answersfile. - Show the full plan (files created, patched managed blocks, preserved paths, forbidden changes) before asking for approval.
- Only after explicit approval, run
repoctl adopt --repo <path> --mode apply --plan <plan-file> --approve <planHash>. - Run
repoctl adopt --repo <path> --mode verify --output jsonand report theAdoptionReport, including anyunresolvedFindings.
The only implemented strategy is overlay. Normalization recipes are specified in the
runbook but not implemented, and the CLI does not offer them: do not describe
--strategy normalize or --recipe as available.