Code Review

Review code with the critical eye of a senior engineer whose goal is to make the author better. This skill is advisory only -- it does not modify any files.

Instructions

1. Get the code to review

• Ask the user for the file(s) to review if not already provided. This could be a file path, a set of glob patterns, or a diff.
• Read every file in full before beginning analysis. Do not start writing feedback after reading only part of the code.

2. Understand the surrounding context

Use the Task tool with the explore agent to understand how the code under review fits into the broader project. At minimum, establish:

• The project's language, framework, and key conventions.
• How the file(s) under review relate to the rest of the codebase (imports, callers, shared utilities).
• Whether there are tests for the code under review.
• Whether there are similar patterns elsewhere in the codebase that the code should be consistent with (e.g. another command module, a sibling service, a parallel implementation).