🔒

Unlock Pro Access

Get unlimited access to all premium prompts and save your favourites.

$5
One-time payment · No subscription · Instant access
600+ exclusive premium prompts
Save prompts across sessions
All future prompt additions
Early access to new categories
Upgrade for $5 →
Claude Coding

Write a Legacy Code Review Checklist

Prompt
Create a checklist reviewing legacy codebases. Include readability and refactoring opportunities.
Why it works

Technical debt accumulates over time without review.

When you're working with legacy code, reviewing it properly is one of the most important things you can do to maintain quality and reduce technical debt. This Claude prompt helps you create a comprehensive legacy code review checklist tailored to your specific codebase. Whether you're a senior developer auditing an older system, a team lead establishing code standards, or someone inheriting a project that's been around for years, this prompt automates the process of identifying readability issues, potential refactoring opportunities, and code smells that have accumulated over time. Rather than starting from scratch with a generic checklist, you get a focused tool that addresses the real challenges of maintaining legacy systems.

Using this prompt is straightforward. You'll fill in placeholders with specific information about your codebase, such as the programming language, the general age of the code, and the specific module or component you want reviewed. For example, if you're reviewing a Python Django application that's been in production for five years, you might input something like "Language: Python, Framework: Django, Age: 5 years, Target: user authentication module." Claude uses these details to generate a checklist that's relevant to your actual situation rather than generic advice.

The output you'll receive from Claude is a practical, itemized checklist covering multiple review dimensions. You'll get sections addressing code readability, potential refactoring opportunities, security concerns, performance bottlenecks, testing gaps, and modernization possibilities. Each checklist item is actionable and specific enough that you can actually use it during your code review rather than getting vague suggestions.

One pro tip for getting better results is to include specific pain points you've already noticed in your codebase. If you know there's duplicated logic in certain areas or you suspect performance issues, mention these upfront. Claude will then prioritize checking those areas and can suggest targeted refactoring strategies, making your review process even more efficient and thorough.