docs: self-host at L1 and ship the three Claude skill adapters
- 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>
This commit is contained in:
co-authored by
Claude Sonnet 5
parent
96d4d08230
commit
7286322c83
@@ -0,0 +1,27 @@
|
||||
---
|
||||
name: repository-adoption
|
||||
description: 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
|
||||
|
||||
1. Run `repoctl adopt --repo <path> --mode assess --output json` (read-only).
|
||||
2. Present the classification, detected content roots, and any `questions` that need
|
||||
owner confirmation.
|
||||
3. Run `repoctl adopt --repo <path> --mode plan --output json` once open questions are
|
||||
resolved. This is still read-only and returns an `AdoptionPlan` with a `planHash`.
|
||||
4. Show the full plan (files created, patched managed blocks, preserved paths,
|
||||
forbidden changes) before asking for approval.
|
||||
5. Only after explicit approval, run
|
||||
`repoctl adopt --repo <path> --mode apply --plan <plan-file> --approve <planHash>`.
|
||||
6. Run `repoctl adopt --repo <path> --mode verify --output json` and report the
|
||||
`AdoptionReport`, including any `unresolvedFindings`.
|
||||
|
||||
Default strategy is `overlay`. Only use `--strategy normalize --recipe
|
||||
documents-to-content-root` when the owner explicitly asks to reorganize root documents.
|
||||
Reference in New Issue
Block a user