repo-audit

Audits repositories with parallel read-only agents and writes verified CLAUDE.md documentation files.

Updated Sep 1, 2026
One-click install
npx skills add https://github.com/Harbour-Emerge/skills --skill repo-audit-harbour-emerge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-audit
Source: https://github.com/Harbour-Emerge/skills/tree/main/repo-audit
Command: npx skills add https://github.com/Harbour-Emerge/skills --skill repo-audit-harbour-emerge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repository documentation is frequently stale or flatly wrong, and onboarding onto an unfamiliar repo wastes hours rediscovering what is actually deployed, which commands really work, and which guards silently fail. This Skill produces a verified mental model of a repo where every load-bearing claim is checked against code. ## Core Features & Use Cases - Parallel read-only analysis: Fans out codebase-analyst agents partitioned by domain (structure, backend, frontend, data, security, deploy) with strict file:line evidence requirements. - Claim verification and reconciliation: Treats existing READMEs and docs as leads, not sources, and resolves agent conflicts by reading the code directly. - CLAUDE.md generation: Writes dated, verified root and per-subdirectory CLAUDE.md files including a high-value Traps section documenting silent failures. - Use Case: When joining a project whose README describes a chatbot but the code is a commerce platform, run this audit to produce accurate orientation docs with cited evidence and a list of misleading traps. ## Quick Start Ask the assistant to audit this repository in depth and generate verified CLAUDE.md files for the root and each significant subdirectory.

Frequently Asked Questions about repo-audit

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

FAQPage Schema
How do I audit an unfamiliar repository with AI agents?

Start with a cheap solo recon of git state, remotes, and manifests, then fan out read-only codebase-analyst agents partitioned by domain such as backend, frontend, data, and security. Require file:line evidence for every claim and reconcile conflicts by reading the code yourself.

How to generate accurate CLAUDE.md files for a repo?

Verify every claim against code before writing, quote commands verbatim from package.json or Makefiles, and date the document with what was verified versus assumed. Include a Traps section describing silent failures with symptom, cause, and check.

Why should existing README files not be trusted during a repo audit?

Existing documentation is frequently stale or wrong, describing deployments that do not exist or features that were never built. Treat READMEs and docs as leads to verify against code, never as sources to restate.

Can parallel agents edit the repository during an audit?

No. The audit agents are strictly read-only and must not edit any file. They are also instructed never to print secret values, reporting only that env files exist with variable names only.

What makes a good traps section in repository documentation?

A trap qualifies if it fails silently or misleads, such as tests that skip when an env var is unset or guards that never fire due to string-typed booleans. Write each trap as the observable symptom, the underlying cause, and the check or fix.