1---
 2name: addressing-agent-comments
 3description: Finds AGENT comments in code, gathers feedback, and carries out requested changes. Use when scanning a repo for inline agent notes, decision requests, or tooling tags.
 4metadata:
 5  source: https://github.com/ampcode/amp-contrib
 6---
 7
 8Search for inline `AGENT:` 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 AGENT: 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 `AGENT:` if none is provided.
192. Use ripgrep to find the tag with context:
20
21```bash
22rg -n --fixed-strings "AGENT:" -C 3
23```
24
253. If multiple tags are used, repeat the search for each tag.
26
27## Review process
28
29- Read each comment with surrounding code to understand scope and intent
30- Make the change or address the concern where feasible
31- If a request is unclear, document assumptions and raise questions
32- Update or remove resolved AGENT: comments
33
34## Output format
35
36- Group findings by file path
37- Include line numbers and relevant context for each comment
38- Summarize key themes and action items at the end
39
40## Expected actions
41
42After finding AGENT: comments:
43
441. Analyze the request in each comment
452. Make the change, or explain why you did not
463. Resolve or update the instruction comment
474. Provide a brief summary of actions taken and any open questions