code-review

To verify code changes comply with a design plan, request a code review that cross-references the diff against your provided design document. It returns precise feedback on plan gaps with traceable references to the plan.

To find subtle bugs like race conditions or resource leaks in a pull request, trigger an explicit code review. It evaluates diffs and PR descriptions to identify edge cases and security issues that automated tests may miss.

You can infer a change's intent by deducing it from commit messages or PR descriptions during a code review. The process ensures the code actually does what the commit messages describe and flags any misalignment.

This code review process does not automatically modify your code when it finds defects. It performs read-only diff analysis and returns precise feedback on bugs and plan gaps without performing any automated edits.

The best way to review code changes against a specific design document is to explicitly request a code review focused on plan compliance. Provide the plan and code changes to receive traceable feedback on defects and plan gaps.

You should explicitly invoke a code review when you need deep bug detection and plan compliance verification, because this skill never triggers automatically and requires a direct request like /code-review to evaluate diffs.