pr-comment-resolver_skill

Overview

This skill is a specialist agent that takes pull request or code review comments, implements the requested changes, and produces a concise resolution report. It streamlines the full comment-to-commit workflow: interpret the feedback, plan edits, make minimal focused changes, verify them, and summarize what was done. Use it to reliably close review items while keeping the codebase consistent and review-ready.

How this skill works

The agent first analyzes the comment to identify the exact code locations, the nature of the request, and any constraints. It then drafts a short plan listing files to modify and possible side effects, applies targeted changes following the repository style, and runs quick verifications to ensure behavior and conventions are preserved. Finally, it generates a clear Comment Resolution Report describing files changed, how the change addresses the comment, and a resolution status.

When to use it

• Address a single PR comment that requires a code change (bug fix, doc update, or minor refactor).
• Systematically fix multiple related code review comments across a PR.
• Respond to reviewer requests for style, naming, or small-logic adjustments.
• Implement requested defensive checks or error handling noted by a reviewer.
• Prepare a concise, reviewer-friendly summary after making code changes.

Best practices

• Always restate your interpretation if the reviewer’s request is ambiguous before making changes.
• Keep edits minimal and focused on the review comment to avoid unrelated churn.
• Follow existing code style and patterns; prefer consistency over introducing new abstractions.
• List potential side effects and related areas that may need follow-up in the report.
• If a requested change would cause problems, propose an alternative and explain trade-offs.

Example use cases

• A reviewer asks to add error handling to a payment processing function — implement try/except, add logging, and report the modified files.
• A code review requests clearer variable names and extraction of validation logic — rename variables, extract a helper, and summarize changes.
• Multiple inline comments call out small style issues — apply targeted fixes and produce a single resolution report.
• A comment requests documentation updates and a minor API tweak — edit docstrings, update function signature, and explain compatibility notes.