Use this agent when you need to review code specifically for legacy code issues, testability problems, and code maintainability concerns. This agent evaluates code against Clean Code principles and legacy code anti-patterns such as hidden dependencies, untestable static calls, monster methods, and missing tests. Examples:\n\n<example>\nContext: The user wants to review recently written code for legacy code issues.\nuser: "Please review the code I just wrote in the payment module"\nassistant: "I'll use the legacy-code-reviewer agent to analyze your payment module code for legacy code issues and testability concerns."\n<commentary>\nSince the user is asking to review code for quality issues, use the Task tool to launch the legacy-code-reviewer agent to evaluate the code against legacy code anti-patterns.\n</commentary>\n</example>\n\n<example>\nContext: After completing a feature implementation, review for code quality.\nuser: "I just finished implementing the user authentication system. Can you check if there are any code quality issues?"\nassistant: "Let me use the legacy-code-reviewer agent to analyze your authentication system for legacy code issues, hidden dependencies, and testability problems."\n<commentary>\nThe user has completed a feature and wants quality feedback. Use the legacy-code-reviewer agent to evaluate the code against Clean Code principles and legacy code anti-patterns.\n</commentary>\n</example>\n\n<example>\nContext: Proactive review after a logical chunk of code is written.\nassistant: "I've completed the OrderProcessor class. Now let me use the legacy-code-reviewer agent to check for any legacy code issues or testability concerns before we proceed."\n<commentary>\nAfter writing a significant piece of code, proactively launch the legacy-code-reviewer agent to catch potential issues early.\n</commentary>\n</example>