Feedback on a GitHub pull request can come from many people. You need to read each comment, understand it, and then fix the code. This skill shows you how to do that step by step using the gh CLI tool.
First, check that you are logged in with gh auth status. Then fetch all comments with gh pr view --comments. Plan your fixes and wait for approval before making changes. After you fix the code, you mark the comments as resolved with a reply.
Avoid common mistakes like fixing code without reading the surrounding lines. Always verify your login first. This skill makes the whole review process clear and organized.
Global
mkdir -p ~/.claude/skills/address-github-commentsProject
mkdir -p .claude/skills/address-github-commentsSource Repository
Caveman Commitjuliusbrussee/caveman
Generate ultra-compressed commit messages with Conventional Commits format
Verification Before Completionobra/superpowers
Always run fresh verification before claiming work is complete or passing
Git Guardrails Claude Codemattpocock/skills
Stop dangerous git commands from running automatically with safety hooks
Setup Pre Commitmattpocock/skills
Automate code formatting type checking and tests before every commit
Using Git Worktreesobra/superpowers
Isolate your feature work with git worktrees and keep your main branch safe
Finishing A Development Branchobra/superpowers
Finish your development branch with merge, pull request, or cleanup options
Resolving Merge Conflictsmattpocock/skills
Resolve Git merge conflicts step by step preserving both intents
Git Commitgithub/awesome-copilot
Automatically write standardized git commits by analyzing your code changes