resolving-pr-issues

resolving-pr-issues is a skill for Claude Code from joaquimscosta/arkhe-claude-plugins. It costs 104 tokens per session (1,531 once invoked), scanned A, original, MIT.

A workflow that checks pull-request review comments against the actual code before applying fixes. A pull request is a proposed code change for review; the workflow can also read a local review report.

In plain words
What is it for?
Use it to process a GitHub pull request or review file, assess each finding, fix confirmed issues, and respond to the reviewers.
Why use it?
It helps avoid making changes for incorrect or low-confidence review suggestions. It gathers comments, verifies them in parallel, presents a triage report for approval, then applies accepted fixes and replies.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to process a GitHub pull request or review file, assess each finding, fix confirmed issues, and respond to the reviewers.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/joaquimscosta/arkhe-claude-plugins/resolving-pr-issues
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.

Any agent
npx skills add joaquimscosta/arkhe-claude-plugins --skill resolving-pr-issues
Clone the repo
git clone --depth 1 https://github.com/joaquimscosta/arkhe-claude-plugins

Made for: Claude Code.

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.

agentmods badge for resolving-pr-issues

README.md
[![agentmods](https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/resolving-pr-issues/github.svg)](https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/resolving-pr-issues)
Your own site
<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/resolving-pr-issues"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/resolving-pr-issues/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.

agentmods 80×15 button for resolving-pr-issues

Your own site · 80×15
<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/resolving-pr-issues"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/resolving-pr-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 104 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,531 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00104 $0.01531
Opus 5.5 $0.00042 $0.00612
Sonnet 5.5 $0.00021 $0.00306
Haiku 4.5 $0.00010 $0.00153

Measured yesterday against content hash e0a29e4d2c5d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

resolving-pr-issues 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 yesterday.

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.

plugins/git/skills/resolving-pr-issues/SKILL.md · 136 lines

How it starts

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

Multi-Agent PR Issue Resolver

Resolve review suggestions using parallel verification and confidence scoring.

Core Principle: Never assume a review comment is correct. Verify every suggestion against actual code before acting.

Input Detection

Detect input mode from $ARGUMENTS:

  • PR mode: argument is a number (123) or contains github.com/starts with http — use gh API
  • File mode: argument contains / or .md or file exists on disk — parse findings from file
  • No argument: show usage hint and stop

Phase 1 — Context Gathering

PR mode — launch 2 parallel Haiku agents:

Agent A — PR Metadata: Run gh pr view $ARGUMENTS --json number,title,body,baseRefName,headRefName,state,author,reviewRequests,statusCheckRollup and gh pr diff $ARGUMENTS. Return: PR summary, base/head branches, CI status, files changed.

Agent B — Comment Extraction: Fetch all review comments using both endpoints:

  • Inline review comments: gh api repos/{owner}/{repo}/pulls/{pr}/comments
  • General issue comments: gh api repos/{owner}/{repo}/issues/{pr}/comments

Return structured list: comment ID, author, type (inline/general), file:line (if inline), body text, resolved status, whether it contains a suggestion code block.

File mode — launch 1 Haiku agent:

Parse the review report file. Extract each finding: description, file:line, category, suggested fix. Detect format from review/skills/code-review/ report template or other common review formats.

Skip conditions: If no unresolved comments/findings exist, report "Nothing to resolve" and stop.

Phase 2 — Parallel Verification

For each unresolved comment/finding, launch a parallel Sonnet agent (batched in groups of 5):

Each agent receives: the comment text, 50 lines of file context around the referenced line, the PR diff (or current branch diff in file mode), and the PR description.

Each agent returns:

Verdict: CONFIRMED | FALSE-POSITIVE | AMBIGUOUS
Category: Blocker | Bug | Code Quality | Style | Question
Confidence: 0-100
Evidence: {what was checked and found}
Suggested resolution: {specific code change or response text}

Read the full file on GitHub · 136 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. yesterday First seen · 136 lines · 104 tokens per session scan A e0a29e4d2c5d

Subscribe to this mod's changes

resolving-pr-issues is a skill published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed yesterday), licensed MIT. It adds 104 tokens to every session and 1,531 once invoked, about $0.0004 per session on Opus 5.5. 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-10-16.