claude-standards-audit

To audit markdown files for standards compliance, this skill maps changed files to relevant authoring rules and runs grep-based pattern checks on the modified content to identify formatting or stylistic violations.

Yes, you can check markdown documentation for banned tokens automatically using this skill's mechanical auditing feature, which executes grep-based pattern matching to detect banned tokens and punctuation violations.

Yes, git integration is required to determine the diff baseline, ensuring the audit checks only relevant, hand-authored markdown files that have been modified on the current branch.

The best way to enforce markdown formatting standards is to run an automated audit on the current branch, mapping prose and documentation files to specific rules and grouping violations by file and line number for targeted fixes.

Markdown linting violations are reported contextually, grouping findings by file and line number to facilitate efficient and targeted fix passes without requiring manual, error-prone review.