Readability and Maintainability Review
Review code like a thoughtful senior engineer.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Review code like a thoughtful senior engineer, with concrete before and after. Language and conventions: [LANGUAGE_AND_CONVENTIONS]. What the code does: [PURPOSE]. Code: [PASTE_CODE]. Team context (experience, how long the code will live): [TEAM_CONTEXT]. Return the five most valuable improvements, each with: BEFORE: the quoted excerpt. PROBLEM: why a reader would struggle (naming, function size, hidden side effects, deep nesting, duplication, unclear errors, magic values, comments that repeat code or lie). AFTER: the revised code. BENEFIT: what gets easier (testing, change, onboarding). RISK: what could break, and the test that proves equal behavior. Then add: three things that are already good and should be kept; a list of smaller nits grouped at the end (not mixed with the main findings); a judgment on whether the code is good enough for its expected lifetime; and one question to the author about intent where the code is ambiguous. Do not rewrite everything, and do not enforce style preferences that the team convention contradicts.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.