Trace documentation claims to code, specs, or upstream documents.
npx skills add https://github.com/usurobor/cnos --skill document-usurobor
Please help me install this Agent Skill. Skill: document Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.eng/skills/eng/document Command: npx skills add https://github.com/usurobor/cnos --skill document-usurobor
Documentation often drifts from reality when claims are not anchored to verifiable sources. This Skill enforces coherence by ensuring every assertion traces to code, specs, or upstream documents and becomes a single source of truth for the project.
Identify a claim in a doc, verify it against the source of truth, and update the documentation accordingly.
High-intent search queries and answers about installing and using this skill.
Prevent documentation drift by tracing every claim to a source of truth like code or specs, verifying assertions before writing and after editing to maintain consistency across READMEs and architecture docs.
A source of truth in documentation is the verifiable origin of a claim, such as source code, specifications, or upstream documents, ensuring every written assertion accurately reflects the current implementation reality.
Verify README claims by identifying specific assertions, tracing them directly to the source code or upstream specs, and updating the documentation to match the verified implementation before and after edits.
Remove stale content from architecture docs by verifying each claim against the current codebase or specs, deleting unverified assertions, and maintaining only versioned, executable examples that match the implementation.
Documentation versioning without executable examples risks drifting from reality. Maintaining versioned, testable examples ensures the documentation remains a verifiable source of truth that matches the current implementation.
team-attentionGenerate a Draft PR from a validated spec using a PR body template.
CaneproAlign design tokens, primitives, and component APIs across products.
vinnie357Generate structured technical documentation with runnable code examples and API references.
ChegginGenerate API references, user guides, and changelogs from code and git history.
