audit

Audit monorepo packages, code, and documentation for inconsistencies and missing content.

10|Updated Sep 24, 2025
One-click install
npx skills add https://github.com/pmcp/nuxt-crouton --skill audit-pmcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/pmcp/nuxt-crouton/tree/main/.claude/skills/audit
Command: npx skills add https://github.com/pmcp/nuxt-crouton --skill audit-pmcp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies gaps and inconsistencies between code and documentation, helping maintain accurate, reliable project records.

Core Features & Use Cases

  • Code and Documentation Audit: Checks for discrepancies between source code, APIs, and written docs.
  • Drift Detection: Finds outdated or missing documentation sections in large monorepos.
  • Review & Verification: Assists teams in verifying docs against current code implementations to ensure accuracy before releases.
  • Use Case: When updating a library, run this Skill to detect undocumented features or obsolete references, ensuring docs reflect the latest code.

Quick Start

Use the audit skill to scan the entire monorepo for documentation drift and generate a detailed report for review.

Frequently Asked Questions about audit

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

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

Detect documentation drift by analyzing project packages, source code, and written materials to identify outdated information, missing content, and inconsistencies between APIs and their documentation.

What is code and documentation consistency verification?

Code and documentation consistency verification is the process of checking for discrepancies between source code implementations and written documentation to ensure project records remain accurate and reliable before releases.

How do I find undocumented features and obsolete references across multiple packages?

Find undocumented features and obsolete references by scanning the entire monorepo to compare dependency tools and source code implementations against written materials, generating a detailed report for review.

Can I verify documentation accuracy against current code implementations for large projects?

Yes, you can verify documentation accuracy against current code implementations for large monorepos with multiple packages and extensive docs by running an audit to compare source code with written materials.

When do I need to run a documentation audit?

Run a documentation audit when updating a library or preparing for a release to detect undocumented features, obsolete references, and gaps, ensuring docs accurately reflect the latest code implementations.