docs-audit-review

Review documentation pull requests against issue requirements and code accuracy.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams prevent inaccurate or incomplete documentation changes from being merged by systematically checking fixes against source issues and current code reality.

Core Features & Use Cases

  • PR Acceptance Review: Compares documentation pull requests against linked issue requirements and verifies that acceptance criteria are satisfied.
  • Accuracy and Regression Checks: Reviews documentation updates for broken references, invalid examples, missing content, and mismatches with the codebase.
  • Workflow Coordination: Orchestrates parallel reviewer agents for multiple documentation PRs and produces approval or change-request outcomes.

Quick Start

Use the docs-audit-review skill to review the provided documentation pull requests against their linked issues and verify they are ready for merge.

Frequently Asked Questions about docs-audit-review

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

FAQPage Schema
How do I validate documentation pull requests against source issues before merging?

Documentation pull request validation systematically compares proposed changes against linked GitHub issue requirements and current codebase accuracy to prevent incorrect merges. It verifies acceptance criteria are satisfied before approving a merge.

What is the best way to check documentation updates for broken references and codebase mismatches?

Checking documentation updates for accuracy involves reviewing changes for broken references, invalid examples, and missing content. It verifies that documentation matches the current source tree reality before integration.

Do I need GitHub CLI access to review documentation PRs against issue requirements?

GitHub CLI access is required to review documentation PRs against issue requirements. The validation process depends on issue retrieval capabilities and source tree verification to approve valid changes or request corrections.

Can I orchestrate parallel reviewer agents for multiple documentation pull requests?

Parallel reviewer agents can be orchestrated to coordinate multiple documentation pull requests simultaneously. This workflow coordination produces structured approval or change-request outcomes for each reviewed PR.

How does issue validation work for documentation fixes in a software engineering workflow?

Issue validation for documentation fixes retrieves linked GitHub issues and checks if pull request changes satisfy stated acceptance criteria. It acts as a merge quality gate to block incomplete or inaccurate updates.

When should I request corrections instead of approving a documentation PR?

Corrections should be requested when a documentation PR contains broken references, invalid examples, or mismatches with the codebase. Valid changes that satisfy source issue acceptance criteria receive approval instead.