verify-docs

Validate file:line references in documentation against the current codebase.

8|2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/SireJeff/k0ntext --skill verify-docs-sirejeff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-docs
Source: https://github.com/SireJeff/k0ntext/tree/main/skills/verify-docs
Command: npx skills add https://github.com/SireJeff/k0ntext --skill verify-docs-sirejeff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that line number references in your documentation accurately reflect the current state of your codebase, preventing outdated information and developer confusion.

Core Features & Use Cases

  • Reference Validation: Automatically checks file:line references within .claude/ documentation against actual code files.
  • Drift Detection: Identifies discrepancies caused by code refactoring, additions, or deletions.
  • Reporting: Generates a clear accuracy report highlighting valid and invalid references.
  • Use Case: After a major code refactor, run this skill to quickly identify and fix all documentation links that are now pointing to the wrong code sections.

Quick Start

Run the verify-docs skill to check all documentation for reference accuracy.

Frequently Asked Questions about verify-docs

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

FAQPage Schema
How do I verify line number references in documentation after refactoring code?

To verify line number references in documentation after refactoring, you can scan for `file:line` patterns and check them against the current codebase to detect drift and report invalid references.

What is documentation drift detection and how does it work?

Documentation drift detection identifies discrepancies caused by code changes by scanning `file:line` patterns in docs, verifying their existence in actual code files, and reporting an accuracy percentage.

How do I check if code references in my docs are still valid?

You can check if code references in docs are valid by running a validation script that scans specified documentation directories for `file:line` patterns and confirms their content matches the codebase.

Can I validate documentation accuracy for a specific directory?

Yes, documentation accuracy validation can target specified directories by scanning for `file:line` patterns within them and verifying the referenced code lines exist and match.

What's the best way to keep documentation in sync with code changes?

The best way to keep documentation in sync with code changes is to automate reference validation, which checks `file:line` links against the codebase and lists invalid references for quick correction.

Why do my documentation links point to the wrong code sections after an update?

Documentation links point to wrong code sections after an update because refactoring shifts line numbers, requiring a validation scan to identify and fix the outdated `file:line` references.