- Move ops/contract.yaml annotation from specification-only to l1-implemented and
declare real content roots for repoctl source, schemas, tests and Claude adapters.
- Add repoctl-cli capability to provides[].
- Route repository.tooling.use and repository.handoff intents to the existing
tooling-implementation KDB topic.
- Update README, AGENTS.md and CLAUDE.md to describe the implemented repoctl surface
instead of a planned one, without claiming L2/L3/MCP capabilities that don't exist.
- Add .claude/skills/{repository-bootstrap,repository-adoption,repo-handoff}/SKILL.md,
generated from the same stewardship.skills_content strings that ship inside every
repoctl init bootstrap (no duplicated logic).
`repoctl validate --repo .` passes with zero findings after this change.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
1.4 KiB
1.4 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 --output jsononce open questions are resolved. This is still read-only and returns anAdoptionPlanwith aplanHash. - 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.
Default strategy is overlay. Only use --strategy normalize --recipe documents-to-content-root when the owner explicitly asks to reorganize root documents.