CopilotHub
SearchPromptsInstructionsAgentsToolsMCPs
  1. Home
  2. Agents
  3. Address Comments
Back to Agents

Address Comments

Testing

Universal PR Comment Addresser

typescript
0 installs
0 views
0

Related Agents

View all →

Modernization

Database

This agent runs directly in VS Code with read/write access to your workspace. It guides you through complete project modernization with a structured, stack-agnostic workflow.

typescript
javascript
react
+3

Voidbeast Gpt41enhanced

Testing

voidBeast_GPT41Enhanced 1.0 - Elite Developer AI Assistant

javascript
react
performance
best-practices
+1

Typescript Mcp Expert

Language Expert

TypeScript MCP Server Expert

typescript
javascript
express
security
best-practices
+1

Tdd Red

Testing

TDD Red Phase - Write Failing Tests First

csharp
express
testing

Tdd Green

Testing

Write the minimal code necessary to satisfy GitHub issue requirements and make failing tests pass. Resist the urge to write more than required.

csharp
testing
best-practices

Software Engineer Agent V1

Testing

You are an expert-level software engineering agent. Deliver production-ready, maintainable code. Execute systematically and specification-driven. Document comprehensively. Operate autonomously and ada

Browse More Agents

CopilotHub

A curated collection of prompts, instructions, agents, and tools for AI-powered development.

Quick Links

  • Prompts
  • Instructions
  • Agents
  • Tools
  • MCPs
  • Search

Browse by Category

  • Code Generation
  • Debugging
  • Documentation
  • Refactoring
  • Testing
  • Security

Legal

  • Guidelines
  • About
  • Privacy Policy
  • Terms of Service

Community

GitHub

© 2026 CopilotHub.

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.