address-github-comments
starsforks
How to install address-github-comments?
sickn33/agentic-awesome-skills/address-github-comments
$npx -y skills add sickn33/agentic-awesome-skills --skill address-github-commentsUse when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
SKILL.md
| 1 | # Address GitHub Comments |
| 2 | |
| 3 | ## Overview |
| 4 | |
| 5 | Efficiently address PR review comments or issue feedback using the GitHub CLI (`gh`). This skill ensures all feedback is addressed systematically. |
| 6 | |
| 7 | ## Prerequisites |
| 8 | |
| 9 | Ensure `gh` is authenticated. |
| 10 | |
| 11 | ```bash |
| 12 | gh auth status |
| 13 | ``` |
| 14 | |
| 15 | If not logged in, run `gh auth login`. |
| 16 | |
| 17 | ## Workflow |
| 18 | |
| 19 | ### 1. Inspect Comments |
| 20 | |
| 21 | Fetch the comments for the current branch's PR. |
| 22 | |
| 23 | ```bash |
| 24 | gh pr view --comments |
| 25 | ``` |
| 26 | |
| 27 | Or use a custom script if available to list threads. |
| 28 | |
| 29 | ### 2. Categorize and Plan |
| 30 | |
| 31 | - List the comments and review threads. |
| 32 | - Propose a fix for each. |
| 33 | - **Wait for user confirmation** on which comments to address first if there are many. |
| 34 | |
| 35 | ### 3. Apply Fixes |
| 36 | |
| 37 | Apply the code changes for the selected comments. |
| 38 | |
| 39 | ### 4. Respond to Comments |
| 40 | |
| 41 | Once fixed, respond to the threads as resolved. |
| 42 | |
| 43 | ```bash |
| 44 | gh pr comment <PR_NUMBER> --body "Addressed in latest commit." |
| 45 | ``` |
| 46 | |
| 47 | ## Common Mistakes |
| 48 | |
| 49 | - **Applying fixes without understanding context**: Always read the surrounding code of a comment. |
| 50 | - **Not verifying auth**: Check `gh auth status` before starting. |
| 51 | |
| 52 | ## When to Use |
| 53 | This skill is applicable to execute the workflow or actions described in the overview. |
| 54 | |
| 55 | ## Limitations |
| 56 | - Use this skill only when the task clearly matches the scope described above. |
| 57 | - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. |
| 58 | - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing. |
People who liked this also viewed
6 picksType
- caveman-commitUltra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. UsSkillsJul 2026
- git-guardrails-claude-codeSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- setup-pre-commitSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- resolving-merge-conflictsSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- using-git-worktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackSkillsJul 2026
- finishing-a-development-branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanupSkillsJul 2026
