home / skills / ampcode / amp-contrib / ampdo

ampdo skill

safe

This skill helps locate AMPDO comments, extract instructions, and apply requested changes across the codebase for faster feedback-driven updates.

npx playbooks add skill ampcode/amp-contrib --skill ampdo

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.2 KB

---
name: ampdo
description: Searches for AMPDO comments in the codebase to gather feedback and execute requested changes.
---

# Ampdo

Search for AMPDO: comments in the codebase to gather feedback and instructions about code changes.

## When to Use

- When reviewing feedback left in the codebase as AMPDO comments
- When looking for inline instructions or change requests
- When processing developer notes embedded in code

## Search Process

Use ripgrep to find AMPDO: comments with context:

```bash
rg "AMPDO:" -C 3
```

## Review Process

- Read each AMPDO comment and surrounding code context
- Take appropriate action based on the feedback: implement requested changes, address issues, or follow instructions
- Present findings organized by file and comment type
- Execute any action items or specific change requests

## Output Format

- Group by file path
- Show line numbers and full context for each AMPDO comment
- Summarize key themes and action items at the end

## Expected Actions

After finding AMPDO: comments:

1. Analyze the feedback or instructions in each comment
2. Implement any requested code changes
3. Address any issues or concerns raised
4. Remove or update AMPDO: comments once addressed
5. Provide a summary of all actions taken

Overview

This skill scans a codebase for AMPDO: comments to gather developer feedback and actionable instructions. It organizes findings by file, shows context and line numbers, and helps implement requested changes. The goal is to convert inline notes into concrete actions and a clear summary of work performed.

How this skill works

The skill uses fast text search (ripgrep recommended) to locate AMPDO: markers with surrounding context. It groups matches by file path, captures line numbers and nearby code, and extracts the intent of each comment. For each item it proposes or performs actions: implement the change, mark the comment addressed, and produce a concise summary of edits and remaining tasks.

When to use it

During code reviews to collect developer feedback embedded in files
When preparing a patch or PR that should address in-code requests
To audit a repository for outstanding AMPDO: instructions
When consolidating scattered developer notes into a prioritized action list
Before a release to ensure inline change requests were resolved

Best practices

Run a repository-wide ripgrep search: rg "AMPDO:" -C 3 to surface comments with context
Read surrounding code to understand intent before making changes
Group findings by file and prioritize by impact and risk
Create small, testable commits for each addressed comment and reference the original AMPDO
Remove or update AMPDO: lines after implementing the requested change to avoid duplicate work

Example use cases

Collect and prioritize QA or developer requests left inline across multiple services
Automate identification of small refactors or TODOs prior to a release
Turn reviewer inline suggestions into discrete pull requests with tests
Maintain a changelog of AMPDO-driven fixes and who implemented them
Quick audit to verify no developer notes were overlooked before merging

FAQ

Do I need ripgrep to use the skill?

Ripgrep is recommended for speed and context flags, but any code search that returns line numbers and nearby lines will work.

What should I do after implementing a requested change?

Update or remove the AMPDO: comment, commit with a message referencing the change, and add the action to the summary of actions taken.