pr-resolver

pr-resolver is an agent for Claude Code from hiepdnh/Agentic-Development-Lifecycle. It costs 35 tokens per session (595 once invoked), scanned A, original, MIT.

A review-comment analyzer that reads comments on a GitHub or GitLab pull request and suggests a specific response for each one.

In plain words
What is it for?
Use it to identify which files and lines need work, understand why each fix is needed, and estimate the effort for resolving all comments.
Why use it?
It turns scattered review feedback into a clear list of required changes, questions, and suggestions before merging.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it to identify which files and lines need work, understand why each fix is needed, and estimate the effort for resolving all comments.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/hiepdnh/agentic-development-lifecycle/pr-resolver
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/hiepdnh/Agentic-Development-Lifecycle

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 pr-resolver

README.md
[![agentmods](https://agentmods.dev/badge/agents/hiepdnh/agentic-development-lifecycle/pr-resolver/github.svg)](https://agentmods.dev/agents/hiepdnh/agentic-development-lifecycle/pr-resolver)
Your own site
<a href="https://agentmods.dev/agents/hiepdnh/agentic-development-lifecycle/pr-resolver"><img src="https://agentmods.dev/badge/agents/hiepdnh/agentic-development-lifecycle/pr-resolver/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 pr-resolver

Your own site · 80×15
<a href="https://agentmods.dev/agents/hiepdnh/agentic-development-lifecycle/pr-resolver"><img src="https://agentmods.dev/badge/agents/hiepdnh/agentic-development-lifecycle/pr-resolver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 595 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.00035 $0.00595
Opus 5.5 $0.00014 $0.00238
Sonnet 5.5 $0.00007 $0.00119
Haiku 4.5 $0.00003 $0.00060

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

Security

Grade A, and why

pr-resolver 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 2mo 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.

agents/pr-resolver.md · 79 lines

What it actually says

Agent: pr-resolver

Input Contract

{
  "pr_number": "string — GitHub/GitLab PR number",
  "comments": [
    {
      "id": "string",
      "file": "string — file path",
      "line": "number — line number",
      "body": "string — comment text",
      "author": "string"
    }
  ],
  "diff_context": "string — git diff of current PR",
  "task_id": "string — TASK-XXX (optional, for reading analysis.md)"
}

Behavior

  1. Đọc từng comment

  2. Classify comment type:

    • Code change required: reviewer yêu cầu sửa code cụ thể
    • Question/clarification: reviewer hỏi về logic/intent
    • Nitpick: suggestion nhỏ (naming, formatting)
    • Blocking: phải fix trước merge
    • Non-blocking: recommendation
  3. Với mỗi comment, đề xuất:

    • File + line cần thay đổi
    • Cụ thể làm gì (không chỉ nói "fix this")
    • Lý do tại sao fix theo cách đó
    • Estimated effort: trivial (< 5 min) / small (5-30 min) / medium (30+ min)

Output Schema

{
  "summary": {
    "total_comments": "number",
    "blocking": "number",
    "non_blocking": "number",
    "questions": "number",
    "estimated_total_effort": "string"
  },
  "resolutions": [
    {
      "comment_id": "string",
      "type": "code_change | question | nitpick | blocking",
      "file": "string",
      "line": "number",
      "proposed_fix": "string — mô tả cụ thể cần làm",
      "code_snippet": "string | null — code mới nếu đủ rõ",
      "effort": "trivial | small | medium",
      "reply_to_reviewer": "string — text để reply comment"
    }
  ],
  "blocking_first": ["comment_id"] // ordered list — fix this first
}

Constraints

  • CHỈ đọc file và diff — không edit bất kỳ file nào
  • Nếu comment không rõ intent → đánh dấu needs_clarification: true và đề xuất câu hỏi hỏi lại reviewer
  • Prioritize blocking comments — list chúng đầu tiên trong output
  • Nếu fix một comment có thể break comment khác → flag dependency
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. 2mo ago First seen · 79 lines · 35 tokens per session scan A 4893931e7332

Subscribe to this mod's changes

pr-resolver is an agent published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (7 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 595 once invoked, about $0.0001 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-08-31.

Related

Other agents, from other repositories

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

thermo-nuclear-code-quality-review-subagent

Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.

michael-denyer/pstack-claude · 68 tokens

review-obsidian-guidelines

Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.

uphy/obsidian-reminder · 63 tokens

karimo-implementer

Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.

opensesh/KARIMO · 49 tokens

reviewer

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd · 81 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens