gentamura/pr-address-bot-reviews
skills/pr-address-bot-reviews/SKILL.md
Use this skill to process bot review feedback on a pull request (for example coderabbitai and chatgpt-codex-operator). Invoke when bot comments arrive and the user wants triage, decision making, and implementation of required fixes.
development
Updated May 5, 2026
$ install --global
skillsauthnpx skillsauth add gentamura/dotfiles pr-address-bot-reviewsInstall 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: May 5, 2026, 9:05 AM144.2s4 files scanned
SKILL.md
- name:
- pr-address-bot-reviews
- description:
- Use this skill to process bot review feedback on a pull request (for example coderabbitai and chatgpt-codex-operator). Invoke when bot comments arrive and the user wants triage, decision making, and implementation of required fixes.
PR Address Bot Reviews
Triage and resolve bot-generated PR feedback with a consistent workflow.
Supported Sources
coderabbitai[bot]chatgpt-codex-operator
Add more bot logins when needed.
Workflow
1. Collect Feedback
- Identify the target PR number (from current branch PR or user input).
- Fetch PR review data with
gh:- reviews
- review comments
- issue comments
- Filter feedback to supported bot authors.
2. Normalize and Group
- Deduplicate repeated suggestions.
- Group by file/path and concern type:
- correctness/bug risk
- security
- performance
- maintainability/style
- test/documentation gaps
3. Decide Actionability
Classify each item into:
must-fix: clear bug/risk/regressionshould-fix: strong improvement with low downsideskip-with-reason: incorrect assumption, out-of-scope, or high-cost low-valueneeds-user-decision: product/architecture tradeoff
4. Implement Needed Changes
- Apply
must-fixand agreedshould-fixitems. - Keep changes scoped to the PR intent.
- Run relevant checks/tests for touched areas.
5. Respond on PR
- For fixed items: reply with what changed.
- For skipped items: reply with concise rationale.
- For tradeoffs: ask explicit decision questions.
- Reply in the correct channel:
- Inline review thread: prefer
skills/pr-address-bot-reviews/scripts/reply-to-review-comment <pr> --login <bot-login> --path <file> [--line <line>] "<response>" - Lower-level flow remains available:
find-review-comment-idthenpr-thread-reply - General PR note: use
gh pr comment
- Inline review thread: prefer
6. Report Back to User
- Summarize by category:
- fixed
- skipped (with reason)
- pending decision
- Provide changed files and verification commands run.
Decision Heuristics
- Prefer concrete evidence over bot confidence.
- Reject suggestions that conflict with project conventions.
- Reject speculative refactors that increase scope without reducing risk.
- Escalate when the fix changes behavior, API contract, or data model.
Minimal Command Sequence
gh pr view <number> --json number,title,body,reviews,comments,files
gh pr view <number> --comments
# preferred single-command inline review reply flow
skills/pr-address-bot-reviews/scripts/reply-to-review-comment <number> --login <bot-login> --path <file> [--line <line>] "<response>"
# lower-level two-step flow when you want explicit control
skills/pr-address-bot-reviews/scripts/find-review-comment-id <number> --login <bot-login> --path <file> [--line <line>]
skills/pr-address-bot-reviews/scripts/pr-thread-reply <number> <comment_id> "<response>"
# optional general PR note
gh pr comment <number> --body "<response>"
# implement code changes
git add <files...>
git commit -m "<message>"
git push
Script Split
scripts/reply-to-review-comment: thin entrypoint that resolves the target review comment id and posts the replyscripts/find-review-comment-id: resolve a single inline review comment id frombot login + path + optional linescripts/pr-thread-reply: post a reply to a known inline review comment id
This keeps comment discovery and reply posting separate internally while still exposing a one-command path for routine use.
Related Skills
gentamura/requirements-to-tasks
tools
VerifiedTrustedCommunity
Use this skill to break down requirements into user stories, acceptance criteria, and actionable tasks. Invoke when starting a new feature or receiving new requirements.
SKILL.mdUpdated May 5, 2026
gentamura/release-runbook
devops
VerifiedTrustedCommunity
Use this skill for release preparation and execution. Invoke when deploying to staging or production environments.
SKILL.mdUpdated May 5, 2026
gentamura/pr-review
development
VerifiedTrustedCommunity
Use this skill to review pull requests against coding standards and best practices. Invoke when reviewing code changes before merge.
SKILL.mdUpdated May 5, 2026
gentamura/pr-create
tools
VerifiedTrustedCommunity
Use this skill to create a pull request from current local changes. Invoke when the user asks to create a branch, commit, push, and open a PR.
SKILL.mdUpdated May 5, 2026