1---
 2name: addressing-code-review-comments
 3description: 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.
 4metadata:
 5  source: https://github.com/ampcode/amp-contrib
 6---
 7
 8Search for inline `CR:` comments, read the surrounding code, and follow through on the request.
 9
10## When to use
11
12- You need to collect and resolve inline agent notes or change requests
13- A repo uses a tag like CR: to point at work items
14- You are asked to scan for inline feedback embedded in code
15
16## Search process
17
181. Identify the instruction tag for the repo. Default to `CR:` if none is provided.
192. Use ripgrep to find the tag with context:
20   ```bash
21   rg -n --fixed-strings "CR:" -C 3
22   ```
233. If multiple tags are used, repeat the search for each tag.
24
25## Review process
26
27- Read each comment with surrounding code to understand scope and intent, maybe the whole file is relevant
28- Make the change, address the concern, or answer the question where feasible
29- If a request is unclear, stop and ask the user to elaborate
30- Update or remove resolved CR: comments
31
32## Output format
33
34- Group findings by file path
35- Include line numbers and relevant context for each comment
36- Summarize key themes and action items at the end
37
38## Expected actions
39
40After finding CR: comments:
41
421. Analyze the request in each comment
432. Make the change or explain why you did not, or answer the question, or otherwise address the comment
443. Resolve or update the comment
454. Provide a brief summary of actions taken and any open questions