doc-audit

Discover repository documentation and dispatch parallel reviewer agents to audit consistency.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/kegbi/monica-companion --skill doc-audit-kegbi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-audit
Source: https://github.com/kegbi/monica-companion/tree/main/.claude/skills/doc-audit
Command: npx skills add https://github.com/kegbi/monica-companion --skill doc-audit-kegbi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end product documentation audit orchestration discovers project docs, dispatches reviewer agents per category, and ensures gaps, user flows, and inconsistencies are identified and resolved before release.

Core Features & Use Cases

  • Discover and classify docs across the repository (roadmaps, product specs, architecture, criteria, testing)
  • Dispatch parallel reviewers per category, collect findings, and present actionable questions to users
  • Re-audit after fixes to verify critical issues are resolved and ensure doc integrity

Quick Start

Train the doc-audit engine to scan the repository and begin the audit workflow with a single invocation.

Frequently Asked Questions about doc-audit

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

FAQPage Schema
How do I automate documentation audit workflows for product releases?

Documentation audit automation works by discovering repository files, dispatching parallel reviewer agents per category, and iterating findings until docs align with product goals. It classifies roadmaps, specs, and architecture documents to resolve gaps and inconsistencies before release.

What is the best way to review repository documentation for consistency and governance?

The best way to review repository documentation is dispatching parallel reviewer agents per category to collect findings and present actionable questions. This cross-references common doc locations with project context to verify consistency, governance, and criteria compliance.

Can I run an end-to-end doc audit on any repository structure?

Yes, you can run an end-to-end doc audit on any repository structure. The engine reads common doc locations and cross-references them with project context, requiring only a frontmatter-defined name and description in SKILL.md to begin scanning.

How do I verify documentation quality after fixing audit findings?

Verify documentation quality after fixes by running a re-audit. The system re-scans updated docs to confirm critical issues are resolved, ensuring documentation integrity and that product goals and criteria are consistently met before release.

Do I need a specific SKILL.md format to start a documentation review?

Yes, you need a SKILL.md file with frontmatter-defined name and description to start a documentation review. Optional resources in scripts/, references/, and assets/ directories provide supplementary context for the audit workflow.