Three-Pass Codebase Audit Workflow
From Wikiprompt, the free prompt encyclopedia
Three-Pass Codebase Audit Workflow A token-efficient three-pass workflow to audit a codebase: map files, audit folder-by-folder, and get a second opinion, minimizing context usage.
Prompt ContentSave
π
Pass 1, the map (Opus 5.5):
"Don't read file contents yet. From the folder tree, file names, sizes and imports, give me one line per file: what it does, and a 1 to 5 guess of how likely it hides dead, duplicated or inconsistent code. Flag anything over 500 lines or not imported anywhere. Table format. Then ask me which folders to open."
Pass 2, the audit (Opus 5.5, one folder at a time):
"Read only [folder]. Find everything broken, inconsistent, inefficient or no longer needed. For each one: file:line, what's wrong, severity (high/med/low), your confidence (sure/unsure). Fix only the sure ones. Keep existing behavior and tests green. No style refactors. Then give me the unsure list as a table."
Pass 3, the second opinion (Fable 5.2, once):
"Here is a list of possible issues another model wasn't sure about, with file paths. Don't re-read the project. For each: fix, ignore, or need more info, one line with the reason. Be blunt."
Sign in to see the full prompt
Continue with:
By logging in, you agree to our Terms of Use and Privacy Policy
Usage
This prompt is designed for use with productivity. Copy the prompt content above and paste it into your preferred AI tool.
For best results, you may customize the placeholders (indicated by square brackets or capital letters) with your specific requirements.
Talk
0 comments