The original title is "Using Claude as a pre-PR code reviewer: a practical workflow"

Short summary

A developer shares a practical workflow for using Claude as an unofficial senior code reviewer, pasting code with targeted questions about scaling, security, and production failure modes. The article outlines four prompt patterns — rubber duck debugging, worst-case analysis, over-engineering checks, and general review — and honestly notes Claude's limitations including hallucinations. The real value is internalizing better practices over time rather than replacing human review.

• •Practical Claude workflow: paste code, ask specific questions about scaling, security, and failure modes
• •Four prompt patterns: rubber duck debugging, worst-case analysis, over-engineering checks, general review
• •Honest about limitations — hallucinations happen, always verify against profilers and metrics

Generated with AI, which can make mistakes.