Review pr comments
Henrique Caiano's custom agent skills (Claude, Codex, herdr). Install with: npx skills@latest add hcaiano/skills
npx -y skills add hcaiano/skills --skill review-pr-commentsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
On-demand review cleanup for an existing PR that has actual feedback: verify each comment, apply valid in-scope fixes in one batched round, respond where useful, and leave the PR merge-ready. Only runs when the user explicitly invokes review-pr-comments.
SKILL.md
2.2 KB, as published. Nobody here has run it
Review PR Comments
Handle real review feedback on an existing PR. This is an on-demand, exception
path: most PRs have no comments because cloud auto-review is disabled and the
heavy review already happened locally (ship-it's dual-review gate). Do not
summon bot reviews (@codex review, @coderabbitai review), and never treat a
bot's silence as something to wait for.
Process, at most TWO rounds (a round = collect → triage → one batched commit → push → required CI green on the new head):
- Collect all open feedback: human reviews, bot comments, unresolved and outdated threads, failing checks.
- Triage each finding against the code:
- Fix in the batch: real correctness, security, or data-integrity issues, and anything a human reviewer explicitly requested.
- Reply, don't push: style nits, defensive hardening for invariants that already hold, severity-inflated or duplicate findings. Answer the thread, resolve it, move on. A nit is never a reason for a push.
- Surface to the user: product/architecture decisions, scope expansions, conflicting reviewer guidance.
- Validate the complete head (original changes plus fixes), commit and push once, and wait for required CI (poll at 60–120 s intervals, never tight loops).
After two rounds, stop pushing: report remaining items with your triage and recommendation. Feedback arriving after your final push does not reopen the loop. Success: required checks green on the final head, human-requested changes addressed, every open thread fixed or answered, and GitHub reports the PR mergeable — bot re-reviews are never a completion requirement.
Do not merge, force-push, modify main, create follow-up PRs (nit-cleanup
follow-up PRs are explicitly banned), or make product and architecture
decisions without authorization.