shipshitdev/gh-address-comments
bundles/github/skills/gh-address-comments/SKILL.md
Resolves GitHub PR review and issue comments by fetching threads, mapping them to code, proposing fixes, and drafting replies for approval. Triggers when the user asks to address PR comments, respond to review feedback, fix review threads, or resolve GitHub comment requests.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library gh-address-commentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 13, 2026, 5:18 AM4.0s2 files scanned
SKILL.md
- name:
- gh-address-comments
- description:
- >-
- disable-model-invocation:
- true
- version:
- 1.0.0
- tags:
- github, pull-requests, review-comments
GH Address Comments
Use this skill when a user wants help resolving PR review or issue comments via the GitHub CLI.
Contract
Inputs:
- Current branch or PR URL/number
- Optional review thread IDs or issue comment IDs
Outputs:
- Review-thread summary
- Mapped code changes
- Draft reply text for each resolved thread
Creates/Modifies:
- Local code changes when fixing review comments
- Does not push or post replies without approval
External Side Effects:
- Reads GitHub PR review and issue comments
- May post GitHub replies only after approval
Confirmation Required:
- Before changing code when fixes are not obvious
- Before pushing
- Before posting replies to GitHub
Delegates To:
code-reviewto validate proposed fixesqa-reviewerbefore final responsegh-fix-ciif fixes cause or reveal CI failures
Workflow
- Verify auth:
gh auth status -h github.com- If not logged in, ask the user to run
gh auth login.
- Identify the PR:
gh pr view --json number,title,url- If no PR is found, ask for the PR URL.
- Collect comments:
- Review comments:
gh api repos/{owner}/{repo}/pulls/{number}/comments - Issue comments:
gh api repos/{owner}/{repo}/issues/{number}/comments
- Review comments:
- Summarize each thread and map to code changes.
- Propose fixes and get user approval before pushing changes.
- Draft reply text for each thread and ask before posting to GitHub.
Notes
- Prefer quoting exact comment text in your summary.
- Keep replies short and specific to the change.
Related Skills
shipshitdev/worktree
development
VerifiedTrustedCommunity
Create an isolated git worktree from the correct base branch and check it out into a clean, gitignored directory. Use when the user asks to make a worktree, spin up a parallel/isolated workspace, work on something without disturbing the current checkout, branch off the current work, or run multiple agents on the same repo at once. Picks the base branch smartly — the current feature branch when you are on one, otherwise the develop integration branch — so worktrees continue your in-progress work by default instead of forking from the wrong place.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/release-cleanup
development
VerifiedTrustedCommunity
Verify a release was fully promoted through develop, staging, and master/main, then prune merged local and remote branches and stale git worktrees. Squash-merge aware — uses GitHub PR merge state as the merge oracle, not commit ancestry. Use when the user asks to clean up branches after a deploy, prune worktrees, remove merged branches, tidy up after promoting develop to staging to master, or confirm nothing stale was left behind before pruning.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/finishing-a-development-branch
development
VerifiedTrustedCommunity
Structured "done coding, now what?" workflow: verify tests pass, detect the repository environment (normal repo vs worktree, named branch vs detached HEAD), present exactly the right merge / PR / keep / discard options, and execute the chosen path including safe worktree cleanup. Use when implementation is complete and the branch needs to be integrated, published, or abandoned.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/feature-intake
tools
VerifiedTrustedCommunity
Capture a client or stakeholder feature request, turn it into a planner-ready PRD epic with scoped sub-issues, check for duplicate work, and place approved issues on a GitHub Projects kanban. Use when a user invokes feature intake, asks to turn a rough client requirement into GitHub issues, or wants an idea written as a PRD and pushed to a board.
27SKILL.mdUpdated Jun 13, 2026