AutoGineer
Generated banner for Address Comments
Generated logo for Address Comments

Address Comments

GitHubOfficialFirst committed by aaronpowellDistributed by GitHub

  • Custom agent
  • Workflow
  • Software development
  • MIT
  • No issues found
Download ZIP

From the author

Address PR comments
— the description by aaronpowell

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The Universal PR Comment Addresser provides a structured approach for developers to process and resolve feedback on pull requests. It emphasizes critical thinking, ensuring that changes are focused, minimal, and accompanied by appropriate test coverage. The skill guides the user through the lifecycle of a comment, from initial assessment and clarification to implementation, testing, and final commit.

What it does

  • Evaluates PR comments to determine if they require action or further clarification.
  • Ensures changes are limited to the scope of the specific comment.
  • Promotes code simplification and minimal implementation.
  • Enforces consistency by applying fixes across all relevant instances.
  • Mandates test coverage for all code modifications.
  • Facilitates a repeatable process for committing changes and moving to the next task.

When to use it

  • When you have received feedback on a pull request and need a structured way to address it.
  • When you need to ensure that your code changes remain focused and do not introduce unnecessary complexity.
  • When you want to ensure that all related issues identified in a comment are resolved consistently.
  • When you need to verify that your fixes are properly tested before committing.

Advantages

  • Reduces the risk of scope creep by focusing strictly on the provided feedback.
  • Improves code quality through consistent application of fixes and mandatory testing.
  • Encourages professional communication by prompting for clarification when comments are unclear.
  • Streamlines the PR resolution process with a clear, step-by-step workflow.

Usage examples

“Address the PR comment suggesting a refactor of the authentication logic.”
The agent will analyze the specific comment, propose a minimal refactor, add necessary tests, and prepare the changes for commit.
“I disagree with this PR comment about variable naming, what should I do?”
The agent will advise you to ask for clarification or provide a rationale for why you believe the current naming is better, following the skill's guidelines.

Install

  1. Download the custom agent as a ZIP:

    https://autogineer.com/agent-skills/github/address-comments/download

  2. Extract the agent file into .github/agents, then commit it:

    mkdir -p .github/agents && unzip -j address-comments.zip 'address-comments/address-comments.agent.md' -d .github/agents

  3. Keep the LICENSE and ATTRIBUTION.md files from the ZIP with your copy.

Documentation by aaronpowell

Universal PR Comment Addresser

Your job is to address comments on your pull request.

When to address or not address comments

Reviewers are normally, but not always right. If a comment does not make sense to you, ask for more clarification. If you do not agree that a comment improves the code, then you should refuse to address it and explain why.

Addressing Comments

  • You should only address the comment provided not make unrelated changes

  • Make your changes as simple as possible and avoid adding excessive code. If you see an opportunity to simplify, take it. Less is more.

  • You should always change all instances of the same issue the comment was about in the changed code.

  • Always add test coverage for you changes if it is not already present.

After Fixing a comment

Run tests

If you do not know how, ask the user.

Commit the changes

You should commit changes with a descriptive commit message.

Fix next comment

Move on to the next comment in the file or ask the user for the next comment.

Files

address-comments.agent.md

Universal PR Comment Addresser

Your job is to address comments on your pull request.

When to address or not address comments

Reviewers are normally, but not always right. If a comment does not make sense to you, ask for more clarification. If you do not agree that a comment improves the code, then you should refuse to address it and explain why.

Addressing Comments

  • You should only address the comment provided not make unrelated changes

  • Make your changes as simple as possible and avoid adding excessive code. If you see an opportunity to simplify, take it. Less is more.

  • You should always change all instances of the same issue the comment was about in the changed code.

  • Always add test coverage for you changes if it is not already present.

After Fixing a comment

Run tests

If you do not know how, ask the user.

Commit the changes

You should commit changes with a descriptive commit message.

Fix next comment

Move on to the next comment in the file or ask the user for the next comment.

Requirements and compatibility

Written for: GitHub Copilot

Works with: GitHub Copilot

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

First committed by
GitHub avatar of aaronpowellaaronpowell
Publisher
GitHub (Official)
Distributed by
GitHub
Source
github/awesome-copilot · agents/address-comments.agent.md · commit 797337f
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
aaronpowell, ilderaj

AutoGineer is not affiliated with or endorsed by aaronpowell or GitHub.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download address-comments.zip