
Address Github Comments
Systematically close the loop on open PR review threads using the GitHub CLI without missing comments or replying before fixes land.
Overview
Address GitHub Comments is an agent skill for the Ship phase that systematically resolves open pull-request review and issue feedback using the authenticated `gh` CLI.
Install
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill address-github-commentsWhat is this skill?
- Verifies `gh auth status` before any PR work
- Fetches threads with `gh pr view --comments` for the current branch
- Categorizes comments, plans fixes, and waits for confirmation when volume is high
- Applies code changes then posts resolution via `gh pr comment`
- Calls out reading surrounding context before editing
Adoption & trust: 611 installs on skills.sh; 40.1k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have an open PR with scattered review threads and no repeatable way to inspect, fix, and mark each comment as addressed.
Who is it for?
Solo builders and small teams who review on GitHub and want agent-guided triage over `gh pr view` and `gh pr comment`.
Skip if: Repos that do not use GitHub PRs, teams forbidden from CLI/git access, or cases where you only need a one-off typo fix with no thread tracking.
When should I use this skill?
You need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
What do I get? / Deliverables
Every selected review thread gets a code fix and a PR comment tying the resolution to your latest commit, ready for re-review or merge.
- Code changes addressing selected comments
- PR comment or thread reply documenting resolution
Recommended Skills
Journey fit
How it compares
Structured PR comment workflow via `gh`, not a generic code-review rubric skill that ignores GitHub threads.
Common Questions / FAQ
Who is address-github-comments for?
Indie and solo developers shipping on GitHub who receive PR reviews and want the agent to drive inspect-plan-fix-respond steps with the official CLI.
When should I use address-github-comments?
Use it during Ship when a pull request has open review or issue comments—after your branch is pushed and before merge—to batch fixes and post threaded replies.
Is address-github-comments safe to install?
It assumes a trusted `gh` session with repo access; review the Security Audits panel on this Prism page and your org’s CLI policies before granting shell and network use.
SKILL.md
READMESKILL.md - Address Github Comments
# Address GitHub Comments ## Overview Efficiently address PR review comments or issue feedback using the GitHub CLI (`gh`). This skill ensures all feedback is addressed systematically. ## Prerequisites Ensure `gh` is authenticated. ```bash gh auth status ``` If not logged in, run `gh auth login`. ## Workflow ### 1. Inspect Comments Fetch the comments for the current branch's PR. ```bash gh pr view --comments ``` Or use a custom script if available to list threads. ### 2. Categorize and Plan - List the comments and review threads. - Propose a fix for each. - **Wait for user confirmation** on which comments to address first if there are many. ### 3. Apply Fixes Apply the code changes for the selected comments. ### 4. Respond to Comments Once fixed, respond to the threads as resolved. ```bash gh pr comment <PR_NUMBER> --body "Addressed in latest commit." ``` ## Common Mistakes - **Applying fixes without understanding context**: Always read the surrounding code of a comment. - **Not verifying auth**: Check `gh auth status` before starting. ## When to Use This skill is applicable to execute the workflow or actions described in the overview. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.