ampdo_skill

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