docs-audit-scan

Audit repository documentation for completeness, accuracy, consistency, and staleness.

1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/bacchus-labs/steamship-integrations --skill docs-audit-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-audit-scan
Source: https://github.com/bacchus-labs/steamship-integrations/tree/main/.wingman/playbooks/skills/docs-audit-scan
Command: npx skills add https://github.com/bacchus-labs/steamship-integrations --skill docs-audit-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify incomplete, inaccurate, inconsistent, and outdated documentation before these issues impact users or development workflows.

Core Features & Use Cases

  • Comprehensive Documentation Auditing: Scans project documentation across completeness, accuracy, consistency, and staleness dimensions.
  • Parallel Review Workflows: Coordinates specialized audit agents to inspect documentation coverage, code references, formatting, and recent changes.
  • Issue-Ready Findings: Synthesizes duplicate findings into prioritized GitHub issues with actionable fixes and acceptance criteria for engineering teams.

Quick Start

Run the docs-audit-scan skill to audit the repository documentation and create implementation-ready GitHub issues for discovered problems.

Frequently Asked Questions about docs-audit-scan

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

FAQPage Schema
How do I find outdated or incomplete documentation in a GitHub repository?

Run a documentation audit scan to evaluate repository files against completeness, accuracy, consistency, and staleness dimensions. It coordinates parallel review workflows to inspect coverage, code references, and recent Git history changes.

Can I automatically generate GitHub issues for documentation gaps?

Yes, this Skill synthesizes duplicate audit findings into prioritized GitHub issues. These generated issues include actionable fixes and acceptance criteria for engineering teams.

Does documentation auditing require Git history access?

Yes, Git history inspection is required to evaluate documentation staleness and recent changes. The audit also needs repository access and issue management tooling to generate prioritized remediation tasks.

What types of software documentation can be audited for consistency?

Auditing applies to READMEs, guides, configuration references, API documentation, workflows, and skill documentation. It scans these files for completeness, accuracy, consistency, and staleness problems.