subagent-doc-check

Detect and classify code, documentation, and CLAUDE rule inconsistencies across a repository.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/Jason-hub-star/GameLab --skill subagent-doc-check-jason-hub-star
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-doc-check
Source: https://github.com/Jason-hub-star/GameLab/tree/main/.claude/skills/gamelab-guide/ops/subagent-doc-check
Command: npx skills add https://github.com/Jason-hub-star/GameLab --skill subagent-doc-check-jason-hub-star

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and summarizes inconsistencies between repository code facts, documentation/status facts, and local CLAUDE rule chains to prevent documentation drift and stale guidance. It helps teams keep documentation and local agent guidance aligned with the actual codebase so decisions and status reports remain accurate.

Core Features & Use Cases

  • Lane-based discovery: Collects three fact lanes (code, docs, rule chain) from configured paths and normalizes them into comparable inventories.
  • Drift detection & classification: Performs pairwise comparisons (code vs docs, code vs rules, docs vs rules) and classifies missing coverage, stale claims, and broken references.
  • Prescriptive reporting: Produces a named drift report with source files and recommended edit surfaces while following a policy that prefers doc/rule updates over blind code mutation.
  • Use case: Run before a status sync or release to surface documentation mismatches, stale CLAUDE guidance, and missing schema or route references.

Quick Start

Run a subagent-doc-check across the repository to collect code, docs, and CLAUDE rule lanes and produce a consolidated drift report highlighting missing coverage and stale claims.

Frequently Asked Questions about subagent-doc-check

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

FAQPage Schema
How do I detect documentation drift in a monorepo codebase?

Detect code-doc-rule drift by collecting code, documentation, and local CLAUDE rule lanes for pairwise comparison, producing a structured report with file-level sources and recommended edit surfaces without direct code mutations.

What is code-doc-rule drift and when do I need to check for it?

Code-doc-rule drift happens when repository code facts, documentation, and CLAUDE rule chains become inconsistent. Run a drift check before status syncs or releases to surface mismatches and broken references.

Can I use this to sync frontend, backend, and documentation teams in a monorepo?

Yes, this applies to monorepo projects for pre-sync audits across frontend, backend, and documentation teams. It identifies missing schema or route references and stale CLAUDE guidance before edits or release decisions.

How do I find stale documentation and missing code coverage references?

Run a lane-based discovery process to normalize code, docs, and rule chains into comparable inventories. Pairwise comparisons classify missing coverage, stale claims, and broken references into a consolidated drift report.

Does the drift detection process automatically modify code to fix inconsistencies?

No, it does not perform direct code mutations. It follows a policy preferring documentation and rule updates over blind code changes, producing a prescriptive report with recommended edit surfaces for review.