check-style

You can validate markdown documentation style by running a lightweight style check on your files before commits. This enforces consistent formatting, heading capitalization, and meta descriptions alignment to ensure Phase 4 compliance.

Yes, you can auto-fix markdown formatting issues by invoking the style check with the --fix flag. This automatically corrects bold formatting and section ordering problems to streamline PR reviews.

The best way to enforce consistent heading capitalization is to use an automated documentation linter. It quickly validates your markdown files and delivers concise reports to speed up your editing workflow.

Yes, pre-commit documentation linting works directly with AGENTS.md and related markdown files. It provides a quick feedback loop to validate Phase 4 formatting compliance during local authoring.

Markdown documentation fails Phase 4 formatting compliance when it violates lightweight rules such as meta descriptions alignment, heading capitalization, and bold formatting. Running a style check identifies these specific issues.

Lightweight markdown style validation focuses strictly on Phase 4 formatting compliance, bold formatting, and section ordering. It does not perform deep semantic analysis or validate complex technical accuracy outside its specific rule set.