Validate markdown documentation with strict mkdocs build checks.
npx skills add https://github.com/CERTCC/Vultron --skill build-docs-certcc
Please help me install this Agent Skill. Skill: build-docs Source: https://github.com/CERTCC/Vultron/tree/main/.agents/skills/build-docs Command: npx skills add https://github.com/CERTCC/Vultron --skill build-docs-certcc
This Skill helps maintain high-quality documentation by verifying that all documentation builds correctly without warnings or broken links, reducing errors in published content.
mkdocs build --strict to detect broken links, missing files, or markdown syntax errors.docs/ directory, initiate this Skill to validate complete, error-free documentation before commit or deployment.Run the build script to verify your documentation in strict mode and fix any reported issues.
High-intent search queries and answers about installing and using this skill.
To validate markdown documentation for broken links, run a strict build process using mkdocs that detects missing files and syntax errors before deployment. This Skill executes mkdocs build --strict to automatically verify all links resolve correctly and markdown syntax passes validation.
Strict build validation works by executing mkdocs build --strict, which treats warnings as errors during documentation compilation. It detects broken internal links, missing files, and markdown syntax errors, causing the build process to fail immediately if any validation issues are found.
Yes, markdownlint-cli2 and mkdocs are required dependencies to perform documentation build validation. Markdownlint-cli2 enforces markdown syntax rules while mkdocs builds the documentation site in strict mode to detect broken links, missing files, and syntax errors during the validation process.
Yes, you can integrate markdown documentation validation into CI/CD pipelines to ensure content is error-free before staging or deployment. Running strict build checks in your pipeline prevents broken links and markdown syntax errors from reaching production, supporting continuous deployment processes.
The best way to prevent broken links in project documentation is to enforce strict build validation checks before commits or deployment. Initiating this validation on the docs directory ensures all internal links resolve correctly and markdown syntax remains consistent across content updates.
Your mkdocs build fails when updating documentation because strict mode treats warnings as errors, catching broken links or missing files introduced during the update. Fix the reported markdown syntax errors and verify all internal links point to existing files to resolve the build failure.
bresendsLint and fix Markdown files using markdownlint-cli2.
windyskyGenerate documentation patterns from code for Sphinx, MkDocs, TypeDoc, and Nextra.
openkaidenRun cargo fmt, clippy, and unit tests before committing.
brainbrewlabsPublishes documentation to GitHub Pages, Vercel, or Netlify from source docs and build outputs.