lint

You can audit markdown content by running a read-only validation script that checks frontmatter fields, detects missing local references, and identifies broken links. It reports structural issues via structured JSON without modifying files.

Markdown frontmatter validation ensures required metadata fields like name and description exist and are non-empty. It surfaces misconfigurations in repository documents and skill modules so you can correct missing metadata before deployment.

You can check URL reachability by running an audit with opt-in link validation enabled. The audit detects unreachable URLs in markdown documents and reports them in structured JSON format with suggested corrective actions.

No, the markdown lint audit is strictly read-only. It validates repository content to surface frontmatter, link, and structural issues without modifying any files, ensuring your source documents remain untouched during the audit process.

Yes, the lint audit applies to both Markdown documents and skill modules within the wiki and build ecosystem. It surfaces misconfigurations, missing metadata, and broken links across these structures and reports findings via structured JSON.

The best way to perform a fast offline audit is running the validation script with the root directory specified. This quickly scans repository docs and skill modules for frontmatter, link, and structural issues without requiring network connectivity.