Home
← Back to templates
Unfamiliar Codebase Analyzer
Programming
Get an outsider's read on an unfamiliar codebase's real structural issues.
Role: You are a senior engineer who just joined an unfamiliar codebase. Context: Codebase: [pasted excerpt: a large controller file mixing business logic, validation, and response formatting] Task: Understand architecture/data flow; identify structural issues, duplication, bottlenecks, maintainability risks; refactoring strategies + improved code. Constraints: Features unchanged, quality only; flag deliberate trade-offs vs. assumed mistakes. Output Format: Architecture summary -> problem areas -> strategy per area -> code.
Expected output
An architecture summary, real problem areas (structural issues, duplication, bottlenecks), a refactoring strategy per area, and improved code — with deliberate trade-offs distinguished from assumed mistakes, not treated the same.
Usage tips
- Paste real, representative code, not a summary — structural issues are only visible in the actual code, not a description of it.
- Check whether a flagged "issue" was actually a deliberate trade-off before refactoring it away — the output tries to distinguish these, but verify with whoever owns the code.
Try it
Fill in the placeholders below and see the compiled prompt update live.
A description or excerpt of the codebase.
- 55
- Words
- 444
- Characters
- 0/1
- Placeholders filled
- 1 min
- Reading time
Quality score11
- Completeness0
- Clarity0
- Context0
- Specificity0
- Constraints0
- Format0
- Output0
- Constraints note100
- Success criteria0
- Scope focus100
- Verification step0
- Negative example0
- Confidence0
- Placeholder syntax100
- Markdown structure0
Suggestions
- Fill in the remaining placeholders.
- Expand your answers — a few words each isn't enough detail for the model to work with.
- Add background context so the model understands the situation.
Role: You are a senior engineer who just joined an unfamiliar codebase.
Context: Codebase: {{CODEBASE}}
Task: Understand architecture/data flow; identify structural issues, duplication, bottlenecks, maintainability risks; refactoring strategies + improved code.
Constraints: Features unchanged, quality only; flag deliberate trade-offs vs. assumed mistakes.
Output Format: Architecture summary -> problem areas -> strategy per area -> code.
AI Assistant