feat(skills): install the agent skills into any repository
The stewardship skills were written by exactly one code path: `init`, which
only runs on a new repository. Adopting an existing one starts from the
repository-adoption skill, and nothing could put that skill there -- so the
entry point to the procedure depended on the operator already having it
from somewhere else. Services/Monitoring carries three domain skills of its
own and no stewardship skill; `adopt` lists `.claude/skills` among its
collision paths and installs nothing.
repoctl skills install --repo . # travels with the repository
repoctl skills install --global # follows the operator everywhere
repoctl skills status --repo .
Scope is stated, never guessed: the two answers differ in who ends up with
the skills, and neither is the obvious default.
No plan and no approval hash. That discipline protects a repository's own
content; this writes only tool-owned files, in a fixed subdirectory, whose
content is fully determined by the installed version. The house rule it
does keep is that a write never destroys what it did not author: a skill
whose content differs is reported as SKILLS_MODIFIED and left alone until
`--force` says otherwise, and the check covers every skill before the first
byte is written, so a refusal leaves nothing half-updated.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
c21ffceef3
commit
c80d39cc73
@@ -6,8 +6,13 @@ This repository defines Repository Stewardship: harness-neutral contracts, knowl
|
||||
|
||||
It now ships an L1 implementation: the `repoctl` CLI (Python package
|
||||
`repository-stewardship`, module `stewardship`, run via `uv run repoctl`) implements
|
||||
`config`, `validate`, `discover`, `describe`, `context`, `init` and `adopt`. Executable
|
||||
`ops/handlers/`, the L2 handler ABI and an MCP server remain planned, not implemented.
|
||||
`config`, `skills`, `validate`, `discover`, `describe`, `context`, `init` and `adopt`.
|
||||
Executable `ops/handlers/`, the L2 handler ABI and an MCP server remain planned, not
|
||||
implemented.
|
||||
|
||||
To work with another repository, put the skills where its agent looks first:
|
||||
`uv run repoctl skills install --repo <path>` (or `--global` once, for every
|
||||
repository). Adoption then starts from the `repository-adoption` skill.
|
||||
|
||||
## Start here
|
||||
|
||||
|
||||
Reference in New Issue
Block a user