repo-doc-audit

Audit repository documentation for inconsistencies and generate a prioritized fix report.

45|13|Updated May 11, 2023
One-click install
npx skills add https://github.com/Open-Earth-Foundation/CityCatalyst --skill repo-doc-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-doc-audit
Source: https://github.com/Open-Earth-Foundation/CityCatalyst/tree/main/.cursor/skills/repo-doc-audit
Command: npx skills add https://github.com/Open-Earth-Foundation/CityCatalyst --skill repo-doc-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs a targeted, one-off audit of a repository's documentation to identify gaps, inconsistencies, and outdated information across docstrings, README files, architecture notes, and scripting conventions.

Core Features & Use Cases

  • Assess README accuracy and completeness, ensuring commands, setup steps, and troubleshooting align with the codebase.
  • Validate architecture and component references against the actual repository structure.
  • Audit script and module docstrings to improve clarity and onboarding.
  • Generate an actionable report with prioritized fixes and suggested edits.

Quick Start

Run the repo-doc-audit skill to generate a full documentation health report for the repository, focusing on README accuracy, architecture references, and script docstrings.

Frequently Asked Questions about repo-doc-audit

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

FAQPage Schema
How do I audit my repository documentation for inconsistencies?

You can audit repository documentation by running a comprehensive health check across docstrings, READMEs, architecture references, and script conventions to identify gaps and generate a prioritized action plan for fixes.

What is a repository documentation health audit?

A repository documentation health audit is a targeted assessment that identifies gaps, inconsistencies, and outdated information across README files, architecture notes, docstrings, and scripting conventions to improve codebase onboarding.

How do I check if my README is accurate after a codebase refactor?

To check README accuracy after a refactor, audit the repository to validate that commands, setup steps, and troubleshooting sections align with the actual codebase structure and generate suggested edits.

Can I validate architecture references against my actual repository structure?

Yes, you can validate architecture and component references by auditing the repository to ensure documentation accurately reflects the actual repository structure and component relationships.

Does this documentation audit work for codebases onboarding new contributors?

Yes, this documentation audit is designed for codebases undergoing refactors, restructures, or onboarding new contributors, providing a prioritized action plan to improve script and module docstring clarity.

What is the best way to generate an action plan for fixing outdated documentation?

The best way to generate a documentation action plan is to perform a repository-wide audit that identifies inconsistencies and produces a prioritized report with suggested fixes for README and architecture alignment.