Respond To Pr Comments In Blocklist
warpdotdev/common-skillsThis skill helps you handle pull request review comments on GitHub. It first fetches any comments that are not already visible. Then it walks you through each comment one by one. You can decide how to respond, make code changes, and preview your reply before posting. No reply goes out without your approval. This saves time and keeps your review process organized.
The skill skips automated bot comments and already-answered threads. It only asks about comments that still need your attention. You can choose to respond to each comment individually or collect all decisions first and then address them in a batch. You stay in full control of every response and resolution.
Developers who review pull requests regularly will find this skill helpful. It turns a messy comment list into a clear step-by-step workflow. Your code changes and replies are previewed before anything is posted to GitHub.
Add Respond To Pr Comments In Blocklist skill to your workflow
Global
mkdir -p ~/.claude/skills/respond-to-pr-comments-in-blocklistProject
mkdir -p .claude/skills/respond-to-pr-comments-in-blocklistSource Repository
More Code Review & Quality Claude Code Skills
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