Repo context document
Skill yarlson/yarstack/plugins/yarstack/skills/repo-context-document
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.From its SKILL.md
npx -y skills add yarlson/yarstack --skill repo-context-documentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.9 KB, 314 tokens by cl100k_base, as published. Nobody here has run it
Repository Context Documentation
Own the information architecture and current-state content under an adopted docs/context/ system.
Workflow
- Confirm requested topics, audience, repository adoption of
docs/context/, dirty-worktree preservation, and authority for moves or removals. - Read all existing context files and the minimum repository evidence needed to verify their claims.
- Classify units by entrypoints, runtime roles, deployment, consumers, state, and contracts rather than directory names.
- Create or update only justified topic files before updating the terse context index.
- Remove stale claims and duplicate facts; merge or remove files only when authorized.
- Verify every edited claim against current implementation.
- Use
english-text-reviewon edited prose and apply material findings 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 implemented responsibilities, ownership, runtime roles, contracts, state, invariants, dependency direction, and concise system flows. 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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.