multiAI Summary Pending
address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
231 stars
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/address-github-comments/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/sickn33/address-github-comments/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/address-github-comments/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How address-github-comments Compares
| Feature / Agent | address-github-comments | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
Which AI agents support this skill?
This skill is compatible with multi.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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.