A command for handling review comments on a GitHub pull request, which is a proposed code change waiting to be merged. It validates the request, analyzes the pull request, and guides the coding agent through resolving the feedback.

Use it with a pull-request URL or number, optionally adding instructions about the changes the reviewer requested.

It organizes the work of understanding reviewer comments and applying the required changes instead of handling each comment manually.

pr-resolve — Command for Claude Code and Cursor by ivangrynenko

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/ivangrynenko/cursorrules

Made for: Claude Code, Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/ivangrynenko/cursorrules/pr-resolve/github.svg)](https://agentmods.dev/commands/ivangrynenko/cursorrules/pr-resolve)

Your own site

<a href="https://agentmods.dev/commands/ivangrynenko/cursorrules/pr-resolve"><img src="https://agentmods.dev/badge/commands/ivangrynenko/cursorrules/pr-resolve/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/ivangrynenko/cursorrules/pr-resolve"><img src="https://agentmods.dev/badge/commands/ivangrynenko/cursorrules/pr-resolve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,268 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01268
Opus 5.5	$0.00000	$0.00507
Sonnet 5.5	$0.00000	$0.00254
Haiku 4.5	$0.00000	$0.00127

Measured 1mo ago against content hash 3ed3235e096e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pr-resolve scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/commands/pr-resolve.md · 129 lines

How it starts

The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Custom Command: PR Resolve

Command Usage

/pr-resolve <pr-url-or-number> [context]

Require the PR URL/number as the first argument. Treat any following text as remediation instructions from the reviewer.

Please address review comments for Pull Request: Use the user-provided arguments (if any) as contextual input. If no artument was provided or you can't read it, stop and ask the user for the prompt, pull request URL and any instructions. Any user input becomes the Use the user-provided arguments (if any) as contextual input. Use those instructions from the Use the user-provided arguments (if any) as contextual input and pull request URL in further steps.

This command uses AI coding agent to efficiently resolve PR feedback while maintaining code quality.

0. VALIDATION PHASE

If no PR link provided in Use the user-provided arguments (if any) as contextual input, ask user: "Please provide the PR link (e.g., https://github.com/org/repo/pull/123 or just the PR number if in the current repo)"

1. ANALYSIS PHASE

Launch initial analysis agent:

Task: "Analyze PR #Use the user-provided arguments (if any) as contextual input comprehensively:
- Use 'gh pr view Use the user-provided arguments (if any) as contextual input' to get PR details
- Use 'gh pr reviews Use the user-provided arguments (if any) as contextual input' to get all review comments
- Use 'gh api repos/{owner}/{repo}/pulls/{number}/comments' for inline file comments
- Check current PR status and CI/CD results
- Categorize feedback into: code changes, test additions, documentation updates
- Check project's AGENTS.md for available testing and linting commands"

2. MULTI-STEP RESOLUTION PHASE

Step 1 - Code Changes & Review Comments

Task: "Address all code review feedback for PR #Use the user-provided arguments (if any) as contextual input:
- For each review comment:
  * Understand the requested change
  * Implement the fix following reviewer suggestions
  * Search codebase for similar patterns to ensure consistency
- For inline file comments:
  * Navigate to exact file and line
  * Implement suggested changes
  * Consider impact on surrounding code
- Make logical commits grouping related changes"

Read the full file on GitHub · 129 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 129 lines · 0 tokens per session scan A 3ed3235e096e

Subscribe to this mod's changes

pr-resolve is a command published in the GitHub repository ivangrynenko/cursorrules (88 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,268 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review Drupal Git and workflow coding-best-practices cursor-rules cursorrules drupal-coding-standards javascript-coding-standards

review-pr

Review a GitHub Pull Request end to end. Use when the user shares a GitHub PR URL or PR number and wants the PR prepared locally for review, analyzed using project rules, optionally commented on in GitHub, and optionally synchronized to Jira based on the review outcome.

edutrul/drupal-ai · 58 tokens

pr-resolve