A tool that creates an Azure DevOps pull request for the current Git branch. It pushes the branch, writes the description using the pull request notes format, chooses a target branch, and adds reviewers.

Use it to publish the current branch as an Azure DevOps pull request, target a branch such as develop, attach a Jira ticket, and request review from selected people or teams.

It brings the steps for opening a reviewed change into one workflow instead of requiring separate branch pushing, description writing, and reviewer setup. It can also use team information or explicit email addresses to resolve reviewers.

ado-open-pr — Skill for Claude Code by jamesyang124/agent-skills

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

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-open-pr/github.svg)](https://agentmods.dev/skills/jamesyang124/agent-skills/ado-open-pr)

Your own site

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

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

When invoked 9,201 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.09201
Opus 5.5	$0.00000	$0.03680
Sonnet 5.5	$0.00000	$0.01840
Haiku 4.5	$0.00000	$0.00920

Measured 7d ago against content hash 0f83541e4ad4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ado-open-pr 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 7d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/complexity.py, scripts/confluence_ticket_log.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.agent-settings/skills/tools/ado-open-pr/SKILL.md · 406 lines

How it starts

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

Create Azure DevOps Pull Request

⚙️ Dependencies

Azure DevOps MCP — provides the repo_* and core_* tools. Install once with the install-azure-devops-mcp skill (writes .mcp.json + ~/.env.mcp-azure-devops), then restart your agent. Repository: https://github.com/microsoft/azure-devops-mcp
generate-pr-notes skill — its note-generation contract is reused for the PR description (see Step 4). Install it globally (~/.claude/skills/generate-pr-notes/) or import it with .agent-settings/skills/import-skills.sh <agent> generate-pr-notes.
Optional: Azure CLI (az, logged in) — used only to identify the current user so they are not added as their own reviewer. Falls back to git config user.email when az is unavailable.
Optional: Confluence credentials in ~/.env.mcp-atlassian (CONFLUENCE_URL, CONFLUENCE_USERNAME, CONFLUENCE_API_TOKEN, written by install-atlassian-mcp) and python3 — used only by Step 6.5.

This skill lives at .agent-settings/skills/tools/ado-open-pr/ and is auto-discovered by import-skills.sh — no manual copy or registry edit is needed.

Arguments

All optional, any order. Disambiguate each bare (unflagged) token as follows:

Token shape	Interpreted as
matches `[A-Z]+-\d+`	Jira ticket
contains `@`	reviewer email / unique name
matches a team key under `teams` in the reviewer config	reviewer team
literally `draft`	open the PR as a draft
anything else	target branch

Flags: --title <text> (explicit PR title), --ado-project <name>, --ado-repo <name>, --no-sync-spec (skip the Step 1.5 spec-alignment scan, which otherwise runs by default), --no-review (skip the Step 1.7 pre-PR review), --review=<keys> (run only these Step 1.7 reviewers, comma-separated from code,security,standards,tests,minimal; refactor is an old name for minimal), --deep (deep review: run all Step 1.7 reviewers twice and the layer-6 tie-break), --no-release-notes (skip the Step 6.5 release-notes page update), --choice=<preview|fix|auto-fix|open> (answer the Step 1.7 question in advance), --fast (fast path, below), --yes (with --fast: skip the final confirmation). Default target branch: see Step 1 item 4.

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

7d ago Changed · +60 lines 0f83541e4ad4
8d ago Changed · +129 lines · -124 tokens per session ca3e06354264
1mo ago First seen · 217 lines · 124 tokens per session scan A fb80d9474ff6

Subscribe to this mod's changes

ado-open-pr is a skill published in the GitHub repository jamesyang124/agent-skills (2 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 9,201 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-31.

Code review Git and workflow

pr

Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.

Yeachan-Heo/oh-my-claudecode · 47 tokens

merge-batch

Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.

diegosouzapw/OmniRoute · 46 tokens

otto-pr-review-loop

Run Polly and OCR on a PR until all findings settle.

omnigent-ai/omnigent · 17 tokens

engram-branch-pr

PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.

Gentleman-Programming/engram · 37 tokens

github-contributor

A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.

daymade/claude-code-skills · 105 tokens

revdiff

Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…

umputun/revdiff · 248 tokens