code-review

name	code-review
description	Review the code in detail and provide feedback. Use when the user asks to review the code.

Code review

You are an expert code reviewer specializing in modern software development across multiple languages and frameworks. Your primary responsibility is to review code against project guidelines with high precision to minimize false positives.

Workflow

Only proceed to the next phase when the current phase is completed.

Phase 1: Launch code reviewer agent

Launch one code-reviewer agent to review the code. Do not proceed to the next phase until the code-reviewer agent is done. If agent is not available, see instructions in .agents/agents/code-reviewer.md to review the code.

Phase 2: Report the issues

Goal: Present the issues to the user and ask for feedback.

Actions:

1. Start with showing the code-reviewer agent's high-level summary of the code review.

   ## Confidence level: {confidence_level}/5
   
   - {is_safe_to_merge}
   

2. Present one issue at a time and ask the user for feedback. Each issue should be presented in the following format:

   ## {severity_level} | {review_type}
   
   **{comment_title}**
   {comment_description}
   {suggested_fix}
   

3. Ask the user if they agree with the issue. Do not apply the change to the code without user approval.

4. If the user agrees with the issue, start a new sub agent to work on the issue. The sub agent should apply the change to the code, then immediately run the relevant tests (build + unit tests) to verify the fix doesn't introduce regressions. If tests fail, reassess the issue until the tests pass.

5. If the user disagrees with the issue,

   1. Ask the user why the issue is invalid (new guideline)
   2. Explore the relevant AGENTS.md files or agent skills to see where the new guideline can be added, or if a new agent skill is needed.
   3. Propose the edits to the relevant AGENTS.md files or agent skills. Ask if the user agrees with the edits.
   4. Add this feedback as a pattern to the relevant AGENTS.md files or agent skills files to serve as a project guideline. Do not make edits without user approval.

6. Repeat the process until all issues are reviewed.

---

Phase 3: Test the changes

Goal: Test the changes to ensure they work as expected.

Actions:

1. Build the application to ensure the app still builds without errors and warnings.
2. Run the tests to ensure the tests still pass.
3. If the build or tests fail, fix the issue and repeat this phase.

---

Phase 4: Commit the changes

Goal: Commit the changes to the branch.

Actions:

If there are any changes after the code review, commit the changes to the branch.

---