Receiving feedback on a pull request is a normal part of coding. You need to check each comment, fix the code, and reply. This can take a lot of time.
Automating the process helps you handle all review comments at once. The system reads every unresolved thread on a pull request. It evaluates each comment and decides if a fix is needed. Then it makes the fix, commits the change, and pushes it. Finally it replies to the thread and marks it as resolved.
You can also target a single comment by providing its URL. The system will only address that specific feedback. It uses a careful approach to avoid unnecessary changes. Most feedback is worth fixing, so it defaults to making the fix unless there is a clear reason not to.
Global
mkdir -p ~/.claude/skills/ce-resolve-pr-feedbackProject
mkdir -p .claude/skills/ce-resolve-pr-feedbackSource Repository
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective