What is ado-pr-resolve-comments?

A tool for reading active review comments on an Azure DevOps pull request and applying the requested code fixes. Azure DevOps is Microsoft's service for hosting code and reviewing changes.

Use it to resolve review threads on an Azure DevOps pull request, preview small fixes, and plan more involved changes before applying them.

It keeps developers from having to copy review comments into a separate task and manually track which fixes were addressed. It asks for consent before making changes and plans larger refactors for review.

ado-pr-resolve-comments — Skill for Claude Code by jamesyang124

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 jamesyang124/agent-skills --skill ado-pr-resolve-comments

Clone the repo

git clone --depth 1 https://github.com/jamesyang124/agent-skills

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jamesyang124/agent-skills/ado-pr-resolve-comments/github.svg)](https://agentmods.dev/skills/jamesyang124/agent-skills/ado-pr-resolve-comments)

Your own site

<a href="https://agentmods.dev/skills/jamesyang124/agent-skills/ado-pr-resolve-comments"><img src="https://agentmods.dev/badge/skills/jamesyang124/agent-skills/ado-pr-resolve-comments/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/skills/jamesyang124/agent-skills/ado-pr-resolve-comments"><img src="https://agentmods.dev/badge/skills/jamesyang124/agent-skills/ado-pr-resolve-comments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

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

Security scan A 1 finding. 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.00087	$0.02603
Opus 5	$0.00044	$0.01301
Sonnet 5	$0.00017	$0.00521
Haiku 4.5	$0.00009	$0.00260

Measured 9d ago against content hash f8cc101e9832, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ado-pr-resolve-comments scanned grade A with 1 finding 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 9d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -fsSL https://raw.githubusercontent.com/mattpocock/skills/main/skills/engineering/diagnose/SKILL.md \

.agent-settings/skills/tools/ado-pr-resolve-comments/SKILL.md · 299 lines

How it starts

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

Azure DevOps PR — Resolve Review Comments

⚙️ Required: install the `diagnose` skill

Install diagnose globally for your agent once, then it is available in all projects.

Claude (global)

mkdir -p ~/.claude/skills/diagnose
curl -fsSL https://raw.githubusercontent.com/mattpocock/skills/main/skills/engineering/diagnose/SKILL.md \
  -o ~/.claude/skills/diagnose/SKILL.md
# Then add to ~/.claude/CLAUDE.md:
# - **diagnose** (`~/.claude/skills/diagnose/SKILL.md`) — bug diagnosis loop

GitHub Copilot (global)

mkdir -p ~/.copilot/skills/diagnose
curl -fsSL https://raw.githubusercontent.com/mattpocock/skills/main/skills/engineering/diagnose/SKILL.md \
  -o ~/.copilot/skills/diagnose/SKILL.md
# Then reference it from your global Copilot instructions file.

Via agent-settings import-skills.sh (project-local)

# If using this agent-settings repo, import it into a project:
.agent-settings/skills/import-skills.sh claude diagnose     # Claude / Copilot

The diagnose skill must be visible to your agent before proceeding.

Reads active PR threads and resolves them by applying fixes, with user consent at every step.

Arguments

Token	Meaning
an Azure DevOps PR URL	required — the PR whose active comments are resolved; parsed in Step 1

No URL → ask for one before doing anything else.

Step 1 — Parse the PR URL

Extract org, project, repo, prId from the URL:

https://dev.azure.com/{org}/{project}/_git/{repo}/pullrequest/{prId}
https://{org}.visualstudio.com/{project}/_git/{repo}/pullrequest/{prId}

Step 2 — Fetch active comment threads

Call mcp_azure_devops__repo_list_pull_request_threads with status: Active.

For each thread that has a threadContext (file + line), extract:

filePath — the file the comment is on
line — the right-side line number
comment — the full comment content
threadId — needed to mark resolved later

Skip system threads (reviewer added, branch updated, etc.) — only process human-authored comment threads.

Read the full file on GitHub · 299 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.

9d ago First seen · 299 lines · 87 tokens per session scan A f8cc101e9832

Subscribe to this mod's changes

ado-pr-resolve-comments is a skill published in the GitHub repository jamesyang124/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 2,603 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review

autoreview

Pre-commit/ship code review: Codex default; optional Claude or Pi.

openclaw/clawhub · 20 tokens

rework-rate

Measure and interpret PR rework rate — the emerging 5th DORA metric.

bradygaster/squad · 20 tokens

omh-code-review

This is a Hermes-native code-review workflow skill.

rlaope/oh-my-hermes · 46 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

code-reviewer

Code review specialist focused on patterns, bugs, security, and performance.

RightNow-AI/openfang · 17 tokens

agent-teams-simplify-and-harden

Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…

LeoYeAI/openclaw-master-skills · 115 tokens

ado-pr-resolve-comments