reviewdoc

Coordinates multi-agent document reviews against defined templates with iterative rounds and git tracking.

Updated Apr 22, 2026

Search Tags:#automation #templates #documentation #multi-agent #review #quality-assurance #git-commit

Ready to run

npx skills add https://github.com/ibalasite/gendoc --skill reviewdoc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reviewdoc
Source: https://github.com/ibalasite/gendoc/tree/main/skills/reviewdoc
Command: npx skills add https://github.com/ibalasite/gendoc --skill reviewdoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures generated documents meet a unified standard by orchestrating template-driven, multi-agent reviews until all findings are resolved.

Core Features & Use Cases

Multi-round review loop driven by templates; reads templates/{TYPE}.review.md to apply reviewer roles, quality-bar, and items from the review checklist.
Supports per-type review rules and cross-file targets (including multi-file BDD or multi-document reviews) to enforce consistent quality across a project.
Produces structured findings, writes remediation suggestions as TODO blocks, and tracks changes via git commits for traceability.

Quick Start

Run /reviewdoc <type> to start the automated, multi-agent review loop.

Frequently Asked Questions about reviewdoc

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

FAQPage Schema

How do I automate multi-agent document reviews against quality templates?▼

Multi-agent document reviews can be automated by coordinating iterative review rounds against templates, ensuring all findings are resolved or escalated. The system reads template files to apply reviewer roles, quality bars, and checklist items consistently.

What is a template-driven review loop for documentation quality assurance?▼

A template-driven review loop is an automated process that reads review templates to apply specific reviewer roles and checklists to generated documents. It runs multiple rounds until all findings are resolved, producing structured remediation suggestions.

How do I track documentation changes and remediation suggestions via git commits?▼

You track documentation changes by running automated reviews that write remediation suggestions as TODO blocks and commit changes via git for traceability. This ensures all modifications and manual review stubs are consistently recorded.

Can I enforce consistent documentation quality across multiple files in a project?▼

Yes, you can enforce consistent quality across multiple files by using per-type review rules and cross-file targets, supporting multi-file BDD or multi-document reviews within a single automated project review loop.

Do I need to create custom templates to start an automated document review?▼

Yes, you need to create review templates formatted as markdown files to define reviewer roles, the quality bar, and checklist items. The review loop reads these templates to apply the specific rules for each document type.

What happens to unresolved findings during an automated multi-agent review?▼

Unresolved findings are either processed through iterative review rounds until resolved or escalated for manual review. The system surfaces findings in a consistent format and creates stubs to track unresolved issues.