Audit a codebase for bugs, risks, and tech debt
A systematic review of a repository with prioritized findings and a remediation plan.
The prompt
Audit this codebase.
Scope: [whole repo / specific modules]
Language and framework: [STACK]
Code: [paste files or point me to the repo structure and key files]
Priorities: [security / reliability / performance / maintainability]
Check for: bugs and logic errors, security vulnerabilities (OWASP Top 10, secrets, injection, auth), error handling, performance problems, concurrency issues, dead code, duplication, outdated or risky dependencies, test coverage gaps, and documentation gaps.
Return:
| # | Finding | File/line | Severity | Evidence | Fix |
Then a remediation roadmap: fix now / next sprint / later.
Report only issues you can see in the code; don't speculate about files you haven't seen.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Software Development prompts
What to fill in
- whole repo / specific modules
- STACK
- paste files or point me to the repo structure and key files
- security / reliability / performance / maintainability
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Learn a programming language or conceptA patient coding tutor that explains concepts, gives exercises, and reviews your solutions.
- Get a beginner-friendly code review of my first projectA ranked set of the five improvements that matter most, explained simply, plus what you did well and what to learn next.
- Refactor code to be cleaner and easier to maintainImproves structure, naming, and design without changing behavior.
- Write a README and publish my first coding project on GitHubA clear README, a safe publishing checklist, and a short post to share what you built.