Files
repoctl/CLAUDE.md
Alexander BaranovandClaude Sonnet 5 7286322c83 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>
2026-08-24 15:00:34 +03:00

11 lines
799 B
Markdown

# CLAUDE.md
@AGENTS.md
## Claude-specific guidance
- Treat `kdb/kdb.yaml` as the routing index, not as a request to read every linked document.
- For bootstrap or adoption work, produce assessment and proposed diff before writing.
- Ask only for decisions that cannot be established from repository evidence, such as ambiguous ownership or source-of-truth conflicts.
- `repoctl` is implemented at L1 (`uv run repoctl ...`); prefer it over manually re-deriving `validate`/`discover`/`describe`/`context`/`init`/`adopt` logic. Only fall back to the documented runbook procedure by hand when `repoctl` is unavailable in the current environment. Do not claim `apply`/`verify` operations, an ABI, or MCP exist beyond what `docs/PLAN.md` "Зафиксированные ограничения" allows.