doc-lint

Audit Markdown documentation for structure, size, duplicates, and SSOT violations.

25|14|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/vlad-ryzhkov/AI-QA-workshop-feb19 --skill doc-lint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-lint
Source: https://github.com/vlad-ryzhkov/AI-QA-workshop-feb19/tree/main/.agents/skills/doc-lint
Command: npx skills add https://github.com/vlad-ryzhkov/AI-QA-workshop-feb19 --skill doc-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill audits documentation quality such as size, structure, duplicates, and SSOT violations to improve maintainability and consistency across artifacts.

Core Features & Use Cases

  • SSOT checks: verify single source of truth and consistency across docs.
  • Structure and size audits: ensure proper document structure and appropriate length.
  • Use Case: When onboarding a new team, run the doc-lint skill to identify orphan sections and duplicate content across the repo.

Quick Start

Run the doc-lint against the project documentation to produce a verification report.

Frequently Asked Questions about doc-lint

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

FAQPage Schema
How do I audit documentation for consistency and SSOT violations?

To audit documentation for consistency and Single Source of Truth (SSOT) violations, you analyze Markdown files to identify duplicate content, orphan sections, and formatting discrepancies. This generates a concise verification report highlighting structural issues.

What is the best way to find duplicate content in a large knowledge base?

Finding duplicate content in a large knowledge base requires scanning Markdown documents to detect overlapping sections and SSOT violations. An audit tool cross-references files to pinpoint duplication and output a report for cleanup.

Can I check Markdown file structure and size for API docs?

Yes, you can check Markdown file structure and size for API docs by running an audit that analyzes document length and formatting. This identifies oversized files and cross-reference integrity issues to ensure consistent quality.

Does doc-lint work on design docs to enforce consistent formatting?

Doc-lint works on design docs by analyzing Markdown files to enforce consistent formatting and verify cross-reference integrity. It audits structure, size, and duplication to maintain quality across large documentation sets.

When do I need to run a documentation quality audit?

You need to run a documentation quality audit when onboarding a new team or maintaining a large knowledge base. It identifies orphan sections, SSOT violations, and oversized Markdown files to ensure structured content.