documentation-build

Validates documentation builds by checking Sphinx or Read the Docs projects for errors and warnings via make targets like html and linkcheck.

29|22|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/canonical/copilot-collections --skill documentation-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-build
Source: https://github.com/canonical/copilot-collections/tree/main/assets/skills/documentation-build
Command: npx skills add https://github.com/canonical/copilot-collections --skill documentation-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that documentation builds correctly, catching errors and warnings before they become larger issues.

Core Features & Use Cases

  • Build Integrity Check: Verifies that documentation tools like Sphinx can successfully build the project's documentation.
  • Error and Warning Reporting: Identifies and categorizes build failures, broken links, and formatting issues.
  • Use Case: Before merging a documentation change, use this Skill to confirm that the updated docs will build without errors on platforms like Read the Docs.

Quick Start

Run the documentation build validation skill on the current project's docs.

Frequently Asked Questions about documentation-build

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

FAQPage Schema
How do I validate a Sphinx documentation build for errors and warnings?

To validate a Sphinx documentation build, you need to identify the documentation directories and execute make targets like 'html' and 'linkcheck'. This process checks for configuration issues, capturing errors and warnings to ensure build integrity.

Why does my Read the Docs documentation build fail before merging?

Your Read the Docs documentation build might fail due to configuration issues, broken links, or formatting errors. Running a build validation helps diagnose these failures by running targets like 'html' and 'linkcheck' to capture exact errors and warnings.

Can I check for broken links in my Sphinx documentation build?

Yes, you can check for broken links in your Sphinx documentation build by running the 'linkcheck' make target. This validation process identifies and categorizes broken links, build failures, and formatting issues before deployment.

What is the best way to ensure documentation integrity before a merge?

The best way to ensure documentation integrity before a merge is to run a validation check on your Sphinx or Read the Docs project. This verifies successful builds, catches configuration issues, and reports errors and warnings early.

Do I need to specify documentation directories to run a build validation?

Yes, you need to specify or identify the correct documentation directories to run a build validation. The process relies on locating these directories to execute the necessary make targets like 'html' and 'linkcheck' for diagnosing failures.