repo-review-docs

Detect documentation truth drift and onboarding gaps in repository reviews.

4|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/danielbaustin/agent-design-language --skill repo-review-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-review-docs
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/repo-review-docs
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill repo-review-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Repo Review Docs skill provides a bounded, role-based lens to verify that repository documentation remains truthful, coherent, and actionable across multi-agent workflows. It focuses on identifying misleading claims, onboarding gaps, and drift between documentation and the actual code, tests, and artifacts.

Core Features & Use Cases

  • Truth-drift detection: flag discrepancies where docs claim behavior not reflected in code or artifacts.
  • Onboarding gap analysis: surface missing prerequisites or unclear setup steps that hinder reproducibility.
  • Documentation governance: track milestone, release, and demo documentation drift and provide structured findings for synthesis.

Quick Start

Review the bounded repository slice and emit a findings-first doc-pack that highlights truth drift, onboarding gaps, and documentation anomalies.

Frequently Asked Questions about repo-review-docs

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

FAQPage Schema
How do I detect documentation truth drift in my repository?

Documentation truth drift is detected by comparing README, demos, release notes, and CLI docs against actual code and artifacts to flag behavioral discrepancies. This process yields a structured findings artifact detailing severity and ownership.

What is an onboarding gap analysis for code repositories?

Onboarding gap analysis surfaces missing prerequisites or unclear setup steps in repository documentation that hinder reproducibility. It reviews bounded repository slices to identify where demos and release notes fail to reflect actual code behavior.

How do I review release notes and demos for misleading claims?

Review release notes and demos for misleading claims by constraining the review to bounded repository slices and checking claimed behavior against code, tests, and artifacts. The output includes a reviewed-doc surface list and a residual risk assessment.

Can I assess residual risk for repository documentation anomalies?

You can assess residual risk for documentation anomalies by applying a bounded review to constrained repository slices where docs claim behavior not reflected in code. The process outputs a residual risk assessment following a shared output contract.

What is the best way to track documentation governance in multi-agent workflows?

Tracking documentation governance in multi-agent workflows requires a bounded, role-based lens to verify repository documentation remains truthful and actionable. It provides structured findings for synthesis to track milestone and release documentation drift.