docs-audit

To find undocumented Rails controllers and models, run a gap audit that inventories application files and resource routes, then compares them against existing documentation pages to produce a prioritized report of missing pages.

A documentation gap analysis for Rails routes compares your application's resource routes against existing doc pages to detect missing user-facing documentation and categorize those gaps by priority based on user impact and feature type.

Yes, you can audit Rails documentation without extra dependencies by using a resource script or standard POSIX find and grep commands to inventory controllers, models, routes, and existing doc pages for comparison.

Prioritize Rails feature documentation before a release by running an audit that classifies missing pages into high, medium, and low priority categories based on user impact, generating an actionable checklist of suggested doc paths.

Yes, the documentation audit works with existing Rails documentation sites by comparing your codebase's controllers, models, and routes against the pages already present on your doc site to identify exactly what is missing.

The best way to generate a checklist of missing Rails doc pages is to run an audit workflow on your project root that inventories all controllers, models, and routes, then outputs a prioritized gap report with suggested documentation paths.