senior-developer

To plan a production-grade code refactor, you first read existing code to preserve project conventions, then define the optimal approach and return a structured payload with file changes, rationale, and tests for the PR workflow.

The best way to approach a bug fix in security-sensitive systems is to evaluate security, error handling, and performance implications during review, ensuring rationale-backed code changes that reduce maintenance overhead.

Code review evaluates architecture and security risks by identifying the optimal approach to feature work or patches, applying a read-before-write discipline to complex multi-language projects and returning structured risk assessments.

Yes, you can use this approach for multi-stack architecture decisions because it applies to complex multi-language projects, producing patch proposals and risk assessments that enforce maintainable code standards.

Reading existing code before writing changes matters because it enforces a read-before-write discipline that preserves project conventions, reducing errors and maintenance overhead across software projects.

A structured payload for a PR workflow patch proposal includes the file changes, rationale, and tests, providing a concise, production-ready code change proposal after reviewing the existing codebase.