doc-standard

Audit Markdown files against a project style guide and propose fixes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/edri2or/project-life-132 --skill doc-standard-edri2or
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-standard
Source: https://github.com/edri2or/project-life-132/tree/main/exported-skills/doc-standard
Command: npx skills add https://github.com/edri2or/project-life-132 --skill doc-standard-edri2or

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures Markdown documentation consistently adheres to the project's house style, reducing review time and drift across docs.

Core Features & Use Cases

  • Load and apply the house style-guide from resources/style-guide.md to any Markdown file.
  • Audit headings, line length, code block language specification, ADR formatting, trailing whitespace, and links to ensure internal references are relative.
  • Propose non-destructive diffs and require explicit user confirmation before applying fixes; re-check after changes.

Quick Start

Run the document-standard enforcer on a Markdown file to apply the house style-guide automatically.

Frequently Asked Questions about doc-standard

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

FAQPage Schema
How do I lint Markdown documentation for style guide violations?

Lint Markdown documentation by loading rules from resources/style-guide.md and auditing target files for heading hierarchy, line length, code block languages, ADR format, trailing whitespace, and relative links to ensure consistency.

What is the best way to enforce ADR formatting standards in Markdown?

Enforce ADR formatting standards by applying linting checks to Markdown files, validating ADR structure against the project style guide, proposing non-destructive diffs, and requiring user confirmation before applying fixes.

How do I validate heading hierarchy and relative links across Markdown files?

Validate heading hierarchy and relative links by auditing Markdown files against the house style guide, checking for structural consistency, and proposing diffs to fix violations before applying changes with user confirmation.

Can I automatically fix trailing whitespace and code block language issues in Markdown?

Automatically fix trailing whitespace and code block language issues by running linting checks on Markdown files, proposing detailed diffs for corrections, and rechecking files after applying user-confirmed fixes.

Does the Markdown linter support non-destructive diffs before applying fixes?

The Markdown linter supports non-destructive diffs by proposing detailed changes for heading hierarchy, line length, and ADR format violations, requiring explicit user confirmation before applying any fixes, then rechecking the file.

Why does my Markdown documentation drift from the project house style?

Markdown documentation drifts from the project house style when files are not audited against a centralized style guide, allowing inconsistencies in heading hierarchy, code block languages, and ADR formatting to accumulate across docs.