---
name: addressing-code-review-comments
description: Finds 'CR:' comments in code, gathers feedback, and carries out requested changes. Use when scanning a repo for inline agent notes, code review from the user, or decision requests.
metadata:
  source: https://github.com/ampcode/amp-contrib
---

Search for inline `CR:` comments, read the surrounding code, and follow through on the request.

## When to use

- You need to collect and resolve inline agent notes or change requests
- A repo uses a tag like CR: to point at work items
- You are asked to scan for inline feedback embedded in code

## Search process

1. Identify the instruction tag for the repo. Default to `CR:` if none is provided.
2. Use ripgrep to find the tag with context:
   ```bash
   rg -n --fixed-strings "CR:" -C 3
   ```
3. If multiple tags are used, repeat the search for each tag.

## Review process

- Read each comment with surrounding code to understand scope and intent, maybe the whole file is relevant
- Make the change, address the concern, or answer the question where feasible
- If a request is unclear, stop and ask the user to elaborate
- Update or remove resolved CR: comments

## Output format

- Group findings by file path
- Include line numbers and relevant context for each comment
- Summarize key themes and action items at the end

## Expected actions

After finding CR: comments:

1. Analyze the request in each comment
2. Make the change or explain why you did not, or answer the question, or otherwise address the comment
3. Resolve or update the comment
4. Provide a brief summary of actions taken and any open questions