ssot-maintenance

Detect and prevent documentation drift across a single-source-of-truth canon using CI lint gates.

23|1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Alexey-Lukin/silken_net --skill ssot-maintenance-alexey-lukin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ssot-maintenance
Source: https://github.com/Alexey-Lukin/silken_net/tree/main/.claude/skills/ssot-maintenance
Command: npx skills add https://github.com/Alexey-Lukin/silken_net --skill ssot-maintenance-alexey-lukin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Large documentation sets drift: the same fact gets restated in multiple files, values diverge, and stale mirrors survive the changes that invalidate them. This Skill provides the operational playbook for keeping a numbered canon of docs (docs/NN_NN_*.md) internally consistent by enforcing that every fact has exactly one canonical home and everything else references it. ## Core Features & Use Cases - Drift hunting and fixing: Follow the hunt → automate → fix loop to find facts restated inconsistently across docs and code, identify the canonical owner, and convert off-home restatements into references. - CI gate operations: Run and interpret the docs lint toolchain (docs:check_refs, docs:toc, tracker:check, docs_band.rb, model/component doc sync gates, wiki:sync) without mistaking a partial green for a full-lane verdict. - Guard authoring recipe: Turn any newly found drift class into a permanent low-false-positive linter, with mutation-verification pitfalls and a catalog of 150+ documented gate-blindness shapes in guard-craft.md. - Use Case: You edit a firmware constant documented in three places. Use this Skill to find the canonical home, update only that location, sweep stale mirrors, and add a linter so the drift can never silently return. ## Quick Start Ask the assistant to check whether a specific value is consistent across the docs and to run the docs lint gates to find any drift.

Frequently Asked Questions about ssot-maintenance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep documentation consistent across many Markdown files?

Assign every fact one canonical home and make all other mentions references rather than restatements. When a fact changes, edit only its home, then run lint gates that flag owner-only vocabulary appearing in other files.

How do I write a documentation linter with low false positives?

Write a pure function that takes file text and returns violation strings, using Unicode-letter boundaries, skipping table rows and fenced code blocks, and exempting the owner document. Unit-test positive, clean, and near-miss cases, then mutation-verify by breaking the check and confirming it fails.

Why is my CI documentation gate green when drift still exists?

A green gate is evidence only about the class it actually inspects. Common causes include the gate's input sitting outside the workflow's path filter, an empty scan scope reading as success, or the gate checking reference resolution rather than semantic correctness.

What is mutation verification for lint rules?

Mutation verification deliberately introduces the defect a gate should catch and confirms the gate goes red, then reverts. It proves the gate catches the intended defect, but says nothing about what the gate cannot see, so both directions must be tested.

Can this approach sync documentation with code structure?

Yes. Registry-sync gates compare canon docs against code trees one-to-one, such as model files against documented model headings and view components against registry rows, failing CI when either side drifts.