Universal PR Comment Addresser

Address PR comments

PublishedJun 17, 2026

Loading actions...

5 minBeginnerprompt21 files

Skill content

Main instructions and any bundled files for this skill.

markdown

Additional Files (20)

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.

Contents

View Original Source

Related Skills

General

PromptBeginner5 minmarkdown

Untitled Skill

193

Jan 12, 2026

General

PromptBeginner5 minmarkdown

Frontend Typescript Linting.mdc

TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend li...

160

Feb 15, 2026

General

PromptBeginner5 minmarkdown

2. Apply Deepthink Protocol (reason about dependencies

risks

127

Jan 15, 2026