pr-review-cycle

Triage and resolve automated code-review findings on open PRs with atomic commits.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/JasperHG90/skills --skill pr-review-cycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-cycle
Source: https://github.com/JasperHG90/skills/tree/main/skills/development/pr-review-cycle
Command: npx skills add https://github.com/JasperHG90/skills --skill pr-review-cycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triages and resolves automated code-review findings on open PRs, one commit at a time, until reviewers are satisfied.

Core Features & Use Cases

  • Identify automated reviewers (Hermes, Gemini, CodeQL, Snyk, Dependabot, or GitHub Actions bots) and fetch the findings.
  • Parse findings by severity and location, propose patches, generate fixes, and commit in logical chunks with conventional commits.
  • Push updates to the PR branch and trigger re-run CI, with user confirmation before any push to prevent history rewrites.

Quick Start

Tell me the PR number and confirm you want me to patch automated findings and push fixes to the PR branch.

Frequently Asked Questions about pr-review-cycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate fixing bot-generated code review findings on a GitHub pull request?

To automate fixing bot-generated code review findings on a pull request, this Skill triages feedback from reviewers like CodeQL, Snyk, and Dependabot, proposes patches, and commits fixes in logical chunks with conventional messages.

Can I automatically patch Snyk and Dependabot vulnerabilities directly on my PR branch?

You can patch Snyk and Dependabot vulnerabilities on your PR branch by having the Skill parse findings by severity, generate fixes, and push atomic commits after receiving explicit user confirmation to prevent history rewrites.

How do I ensure CI re-runs after patching automated code review findings?

To ensure CI re-runs after patching automated code review findings, the Skill pushes updates to the PR branch and triggers a verification of the re-run CI process once all reviewer findings are resolved.

Does this approach require manual confirmation before pushing fixes to the PR branch?

Yes, this approach requires explicit user confirmation before pushing any fixes to the PR branch, ensuring you maintain control over history rewrites and commit integrity during the automated patching workflow.

What is the best way to group automated pull request fixes into conventional commits?

The best way to group automated pull request fixes into conventional commits is by parsing findings by severity and location, generating patches, and committing them in logical chunks one commit at a time until reviewers are satisfied.