Create, update, or consolidate adopted current-state documentation under docs/context/. Use for durable implemented architecture, ownership, runtime, domain, flow, terminology, or engineering-practice context.
Installs into .claude/skills of the current project.
Are you the author of Repo Context Document?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/yarlson-repo-context-document)
---
name: repo-context-document
description: Create, update, or consolidate adopted current-state documentation under docs/context/. Use for durable implemented architecture, ownership, runtime, domain, flow, terminology, or engineering-practice context.
---
# Repository Context Documentation
Own the information architecture and current-state content under an adopted `docs/context/` system.
## Workflow
1. Confirm requested topics, audience, repository adoption of `docs/context/`, dirty-worktree preservation, and authority for moves or removals.
2. Read all existing context files and the minimum repository evidence needed to verify their claims.
3. Classify units by entrypoints, runtime roles, deployment, consumers, state, and contracts rather than directory names.
4. Create or update only justified topic files, then update the system's index file, such as `docs/context/README.md`, if it has one.
5. Remove stale claims and duplicate facts; merge or remove files only when authorized.
6. Verify every edited claim against the current implementation, and link it to the file, test, or configuration that shows it.
7. Use `text-improve` on edited prose without weakening architectural precision or established terminology.
Write only under `docs/context/`. Use `docs-drift-review` for incidental change-caused drift, `docs-review` for general documentation, and `critical-journey-document` for actor-goal journeys. Link to canonical plans, specifications, runbooks, guides, and API references instead of duplicating them.
Record what a reader cannot get quickly from the code: implemented responsibilities, ownership, runtime roles, contracts, state, invariants, dependency direction, and flows that cross components. Context that restates the code costs every reader time and goes stale. Exclude history, progress, raw file inventories, speculative design, TODO lists, duplicated instructions, and sensitive values.
Do not impose `docs/context/` on a repository that has not adopted it without an explicit request.
Finish with the context files created, updated, consolidated, or removed and the evidence used.
