Repository auditing
Purpose, technology, git history, dependencies, maintenance state, reusable assets and security, from a single agent.
Repository portfolio audit
RepoAudit
Know what every repository is for before you spend an hour re-learning it.
Read-only AI agents audit a folder of repositories and return one evidence-backed recommendation per repository: continue, archive, delete-candidate or investigate.
Where it is today Working tool, used on our own repositories
The problem
Repositories pile up faster than anyone retires them
Tutorials cloned once, experiments never finished, forks nobody changed, and real projects mixed in among them. Deciding what to keep normally means opening each one and reconstructing its history from memory.
Built for
- Engineering leads with a sprawling GitHub or Azure DevOps estate
- Platform teams planning a clean-up or migration
- Technical due diligence
What it does
Capabilities
Specialised reviews
Architecture, security, cloud and infrastructure-as-code, and testing reviews run only where the repository warrants them.
Evidence, not vibes
Observed facts are kept separate from inferences. Each recommendation states its confidence and what could not be determined.
Read-only by design
The auditing agents hold no file-write tool. Nothing is archived, deleted, committed or pushed automatically; the decision stays with a person.
Set up what you keep
For the repositories you decide to continue, a separate agent documents their real conventions so AI coding tools work well in them.
How it works
The flow
- Repository
- Audit
- Specialised analysis
- Evidence
- Classification
- Optional configuration
Try it
Audit a sample repository
Pick one of four sample repositories and watch the audit reach its recommendation.
$ audit ./terraform-aks-sample
- Audit
- Purpose: Terraform sample that creates one AKS cluster
- Last commit four years ago, one contributor
- No CI workflow, no tests
- Cloud review
- Provider versions pinned to an old major release
- Cluster module is small and readable
- Evidence
- Observed: no references from other repositories
- Inferred: learning exercise, not a running system
ARCHIVE
Keep the cluster module as a reusable snippet; archive the repository. Confidence: medium.
Simulated walkthrough with sample data. Nothing here connects to a live system.
Built with
Technology
- Claude Code
- Claude Code plugins
- Markdown agent contracts
- Git
- PowerShell
Stated plainly
Limitations
- Runs inside Claude Code in your environment; it is not a hosted service yet.
- It recommends; it never archives or deletes anything itself.
- Its time saved per repository has not been measured yet, so we do not quote a number.
See RepoAudit on your environment.
Tell us where you are. An engineer replies with a proposal, not a sales script.
All products