code-review

To review a pull request for security and performance, this Skill systematically examines code changes against established engineering practices, identifying runtime errors, security flaws, and bottlenecks before providing structured feedback.

Ensuring adequate test coverage during a code review involves verifying functional, integration, and end-to-end tests. This Skill checks the attached code changes to confirm sufficient testing exists before merging pull requests.

Yes, you can assess architectural alignment and component interactions. The Skill performs design assessments to evaluate how well new code changes adhere to the established project architecture and engineering practices.

Yes, the code review process evaluates long-term impact and maintainability. It follows specific guidelines to assess design, verify test coverage, and identify potential problems affecting software quality over time.

A comprehensive code review checklist for software quality should cover runtime errors, performance bottlenecks, security vulnerabilities, architectural alignment, and test coverage verification to ensure maintainability.

You need a structured code review process when merging new features or examining code changes. It helps systematically identify bugs, assess design, verify tests, and ensure long-term software quality before integration.