docs-lint

Validate documentation links, source references, and MkDocs compliance.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/arakitakashi/homework-coach-robo --skill docs-lint-arakitakashi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-lint
Source: https://github.com/arakitakashi/homework-coach-robo/tree/main/ref/adk-streaming-guide-main/.claude/skills/docs-lint
Command: npx skills add https://github.com/arakitakashi/homework-coach-robo --skill docs-lint-arakitakashi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, git, python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining high-quality, consistent documentation by automating the review of external links, source code references, and adherence to style guidelines.

Core Features & Use Cases

  • Link Validation: Automatically checks all external links within documentation files for validity (e.g., 404 errors, timeouts).
  • Source Reference Checking: Validates that code snippets referenced in documentation still exist in their original locations in linked repositories, auto-fixing drift.
  • Style and Formatting Compliance: Ensures adherence to documentation style guides and platform-specific requirements (e.g., MkDocs compliance).
  • Use Case: Before merging a new set of documentation pages, run this Skill to catch broken links and ensure all code examples are up-to-date and correctly referenced, preventing user confusion and maintaining a professional standard.

Quick Start

Run the docs-lint skill to check all external links and source code references in the documentation.

Frequently Asked Questions about docs-lint

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

FAQPage Schema
How do I automate link validation and check for broken external links in documentation?

Automate link validation by running checks against all external links in your documentation files to catch 404 errors and timeouts. This ensures external link validity and prevents broken references before merging documentation pages.

How do I prevent code drift between documentation snippets and source code references?

Prevent code drift by validating that code snippets referenced in documentation still exist in their original locations within linked repositories. This source reference checking automatically detects and can auto-fix drift against sibling repositories.

How do I enforce a documentation style guide and ensure MkDocs compliance?

Enforce a documentation style guide by checking structural consistency, style, and formatting across all documentation parts. This includes specific validation for MkDocs compliance to ensure adherence to platform-specific requirements.

Do I need Python3 and git installed to run documentation linting checks?

Yes, you need Python3 and git installed to run documentation linting checks. These dependencies are required to execute the validation scripts, check source code references, and interact with linked repositories for drift detection.

What is the best way to validate documentation content before merging new pages?

The best way to validate documentation content before merging is to run automated checks for broken external links, verify source code references are up-to-date, and ensure style guide compliance. This prevents user confusion and maintains professional standards.