Files
repoctl/.claude/skills/repo-handoff/SKILL.md
T
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

870 B

name, description
name description
repo-handoff Produce a minimal, intent-scoped context handoff for a repository using repoctl context. Use when another agent, session or teammate needs just enough context to work on one task in a repository.

repo-handoff

Thin wrapper around repoctl context. Do not read the full repository or the full KDB by hand when this skill applies — let repoctl perform the selection.

Procedure

  1. Turn the user's request into an intent id (e.g. container.deploy, repository.adopt), not a literal command.
  2. Run repoctl context --repo <name-or-path> --intent <intent> --output json.
  3. If the bundle looks incomplete, retry with --include-related or --materialize and an explicit --budget-bytes.
  4. Hand the resulting ContextBundle (and any warnings) to the requester instead of pasting raw repository files.