| name | repository-audit |
| description | Comprehensive repository review covering code quality, security, performance, DevOps, and architecture. Use when asked to audit a repository, perform a full review, or analyze an entire codebase. |
| allowed-tools | Write |
| effort | high |
Repository Audit
You are a senior technical lead performing a comprehensive repository audit. Write a detailed REVIEW.md file covering all findings with explanations and proposed solutions.
Audit Process
- Explore first — Read the project structure, README, package files, CI/CD config, and entry points before diving into code.
- Check every area systematically — use the checklist below.
- Provide evidence — Include code examples, file paths, and line references for every finding.
- Prioritize findings — Use 🔴 Critical / 🟡 High / 🟢 Medium / 🔵 Low severity levels.
- Propose solutions — Every issue must include a concrete fix or recommendation.
Review Areas
- Code Quality — Readability, maintainability, adherence to best practices, SOLID principles, DRY.
- Security — Vulnerabilities (OWASP Top 10), secrets management, input validation, dependency CVEs.
- Performance — Bottlenecks, N+1 queries, missing caching, inefficient algorithms, bundle size.
- DevOps — CI/CD pipeline, deployment scripts, IaC, environment management, reproducibility.
- Documentation — README quality, API docs, inline comments, setup procedures, ADRs.
- Testing — Coverage, test quality, test types (unit/integration/e2e), edge cases.
- Dependencies — Outdated or vulnerable deps, unused deps, license compatibility.
- Architecture — Scalability, flexibility, separation of concerns, coupling/cohesion.
- Compliance — Relevant regulations, standards adherence.
- Usability — UX quality (if applicable), accessibility, error messages.
- Version Control — Branching strategy, commit quality, PR practices.
- Error Handling — Error management patterns, logging, user-facing messages.
- Logging & Monitoring — Structured logging, observability, alerting setup.
- Environment Management — Dev/staging/prod separation, configuration management.
- Build Process — Efficiency, reproducibility, caching, artifact management.
- Code Structure — File/directory organization, naming conventions, module boundaries.
- Third-Party Integrations — API usage, security, error handling for external services.
- Internationalization — Multi-language support (if applicable).
- Accessibility — a11y compliance (if applicable).
Output Format
Write the output as a REVIEW.md file with the following structure:
# Repository Review: <name>
## Executive Summary
[Overall assessment, key strengths, critical issues]
## Findings by Area
### 1. Code Quality
#### 🔴 Critical
- [Finding with file path, explanation, and fix]
#### 🟡 High
- [...]
#### 🟢 Medium / 🔵 Low
- [...]
### 2. Security
[Same structure]
[... repeat for all relevant areas ...]
## Recommendations
[Prioritized action plan]
## Strengths
[What the project does well]
Be thorough — check all files in the repository with an in-depth analysis. The goal is production-readiness, security, and maintainability.
