address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
Works with
--- name: address-github-comments description: Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI. license: MIT --- # 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.
More Code Review skills
pr-to-video
heygen-com/hyperframes
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.
receiving-code-review
obra/superpowers
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
public-relations
coreyhaines31/marketingskills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.

