Run Code Review and resolve findings

Ask for a code review, read its coverage, and resolve actionable findings.

Before you start

Finish the implementation turn and inspect its changed files first. Code Review is another agent pass; it can take time and provider resources.

The demo review reports No findings and names its coverage: one changed file, inspected without running tests. The manual accessibility check above it remains unperformed.

Step by step

1. Open the implementation conversation and choose Code review near the composer. The conversation shows Sent for code review and a Reviewing activity while the pass runs.

2. Read the resulting Code review card. Check Coverage to understand which files were inspected and any limitations.

3. If findings are present, read the issue, what happens, and suggested fix. Open referenced code and decide which findings apply to the intended behavior.

4. Select the findings you want addressed and choose Fix selected, or use Fix all when all pending findings should be addressed.

5. Inspect the resulting edits and repeat relevant checks. A request to fix findings starts more work; it does not immediately prove those findings are resolved.

6. If the result says No findings, still read its coverage and complete any remaining manual checks before delivery.

What to expect

You have a review result tied to the conversation’s changed code and a deliberate response to any findings.

Troubleshooting and useful details

The demo review inspected one file and explicitly ran no tests or commands during its read-only review. No findings means no issues were reported within that review’s coverage. Coverage not confirmed is a different result and should not be treated as a clean review. Use tests and runtime checks alongside this feedback.