address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
Target: Software development & testing. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Address GitHub Comments
- Overview
- Prerequisites
- Workflow
- 1. Inspect Comments
- 2. Categorize and Plan
- 3. Apply Fixes
- 4. Respond to Comments
Efficiently address PR review comments or issue feedback using the GitHub CLI (gh). This skill ensures all feedback is addressed systematically. Ensure gh is authenticated. If not logged in, run gh auth login. Fetch the comments for the current branch's PR. Or use a custom script if available to list threads. 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. Apply the code changes for the selected comments. Once fixed, respond to the threads as resolved. Applying fixes without understanding context: Always read the surrounding code of a comment. Not verifying auth: Check gh auth status before starting.
- Source repository
- davila7/claude-code-templates
- Source file
- cli-tool/components/skills/productivity/address-github-comments/SKILL.md
- Fixed revision
- 21be197f100a12b8d0dd9a211cc244c8179f84d3
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: davila7/claude-code-templates · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T15:01:39.604Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.