repo-auditor-pro

Audit software repositories for release readiness and maintainability risks.

8|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/drewid74/ai_skills --skill repo-auditor-pro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-auditor-pro
Source: https://github.com/drewid74/ai_skills/tree/main/repo-auditor-pro
Command: npx skills add https://github.com/drewid74/ai_skills --skill repo-auditor-pro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you determine whether a code repository is ready to release by checking the presence and adequacy of critical files, validating documentation links, detecting stale or placeholder content, and confirming basic automation coverage without inventing anything not found in the repo.

Core Features & Use Cases

  • Release readiness scoring: Checks for required baseline hygiene like README, LICENSE, .gitignore, CONTRIBUTING, and presence of CI workflows.
  • Structural integrity verification: Flags missing or weak foundational files that block usability, legal clarity, or contributor onboarding.
  • Docs and content consistency checks: Detects broken internal/external links, stale doc references to non-existent files, and TODO/FIXME/placeholder text that should not ship.
  • Prioritized action plan: Produces an executive summary plus categorized findings and a next-step plan focused on severity.

Quick Start

Use repo-auditor-pro to audit the current repository for release readiness, including missing baseline files, broken links, stale documentation references, TODO/placeholder content, and whether CI is present and passing.

Frequently Asked Questions about repo-auditor-pro

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

FAQPage Schema
How do I check if my repository is ready for an open source release?

To check repository release readiness, audit required baseline files like README, LICENSE, .gitignore, and CONTRIBUTING, validate documentation links, and confirm CI workflows are present and passing.

What does a repository release readiness audit include?

A repository release readiness audit includes structural integrity verification of baseline files, documentation consistency checks for broken links, stale references, and placeholder text, plus CI quality gate validation.

How do I find broken documentation links and stale references before publishing?

Finding broken documentation links and stale references requires deterministic file discovery and internal/external link resolution to flag missing resources, returning the exact path and line as evidence.

How do I scan my codebase for TODO and FIXME placeholder text that should not ship?

Scanning for TODO and FIXME placeholder text involves content scanning across the repository to detect stale or incomplete sections, ensuring these placeholders do not ship in a release.

Can I use a repository audit for troubleshooting incomplete documentation?

Yes, you can use a repository audit for troubleshooting when documentation is incomplete, inconsistent, or references missing resources by generating a prioritized action plan based on severity.

Does a repository audit check if CI workflows are present and passing?

Yes, a repository audit checks if CI workflows are present and passing by confirming basic automation coverage as part of its release readiness scoring and maintainability risk assessment.