pr-azdo

pr-azdo is a skill for Claude Code from chan4lk/specclaw. It costs 59 tokens per session (662 once invoked), scanned A, original, MIT.

A workflow for creating a pull request in Azure DevOps, Microsoft’s code-hosting and project-management service. It requires a verified change and includes the project’s planning and verification records.

In plain words
What is it for?
Use it when the project stores code in Azure DevOps instead of GitHub. It creates the request, builds its title and description from the change documents, and records the resulting URL.
Why use it?
It prevents a pull request from being opened before the change has passed its checks or without the related planning documents. It also handles the Azure DevOps API details for the project.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the specclaw plugin — 32 skills, 21 agents shipped together

Good fit Use it when the project stores code in Azure DevOps instead of GitHub. It creates the request, builds its title and description from the change documents, and records the resulting URL.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chan4lk/specclaw/pr-azdo
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 chan4lk/specclaw --skill pr-azdo
Clone the repo
git clone --depth 1 https://github.com/chan4lk/specclaw

Made for: Claude Code.

Or install specclaw, the plugin that ships this one along with the rest of its 32 skills, 21 agents.

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-azdo

README.md
[![agentmods](https://agentmods.dev/badge/skills/chan4lk/specclaw/pr-azdo/github.svg)](https://agentmods.dev/skills/chan4lk/specclaw/pr-azdo)
Your own site
<a href="https://agentmods.dev/skills/chan4lk/specclaw/pr-azdo"><img src="https://agentmods.dev/badge/skills/chan4lk/specclaw/pr-azdo/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-azdo

Your own site · 80×15
<a href="https://agentmods.dev/skills/chan4lk/specclaw/pr-azdo"><img src="https://agentmods.dev/badge/skills/chan4lk/specclaw/pr-azdo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 662 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.00059 $0.00662
Opus 5 $0.00030 $0.00331
Sonnet 5 $0.00012 $0.00132
Haiku 4.5 $0.00006 $0.00066

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

Security

Grade A, and why

pr-azdo 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 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.

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/specclaw/skills/pr-azdo/SKILL.md · 25 lines

What it actually says

specclaw pr-azdo

First, run specclaw-ensure-init .specclaw — idempotently creates .specclaw/ if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).

Create an Azure DevOps PR for a verified change.

  1. Validate: specclaw-validate-change .specclaw <change> pr. Fails if verify-report.md is missing.
  2. Run: specclaw-azdo-pr .specclaw <change>always create the PR through this script, never hand-roll the ADO REST call. specclaw-azdo-pr stages and commits the full .specclaw/changes/<change>/ planning trail (proposal, spec, design, tasks, status, verify-report) into the branch and aborts if any of it is left uncommitted — bypassing it ships a PR missing the proposal artifacts.
    • Requires AZDO_TOKEN, AZDO_ORG, AZDO_PROJECT, AZDO_REPO (set via /specclaw:auth-azdo).
    • Test policy: same gate as /specclaw:pr — prompts once, enforces on all runs.
    • PR creation: builds title (≤128 chars) from proposal.md, description from spec.md + verify-report.md, calls ADO REST API.
    • Saves URL: appends **ADO PR:** <url> to status.md.
  3. Update project context: After the ADO PR URL is saved, rewrite .specclaw/context.md to incorporate decisions from this change:
    • Run specclaw-update-context .specclaw <change> — this outputs an LLM prompt.
    • Feed the prompt to a coding agent that rewrites context.md in place (architecture-doc style: replaces stale info, merges new decisions).
    • If context.md changed, commit it: git add .specclaw/context.md && git commit -m "docs(context): update project context after <change>" and push.
    • Errors here are non-blocking — warn and continue.
  4. Report the ADO PR URL to the user.

CI outer loop (if loop.ci_gate: true): once the PR branch is pushed, the CI tier of /specclaw:loop (Step 3 / specclaw-loop ci-poll) polls Azure Pipelines runs and iterates fixes until they are green, or loop.ci_max_iterations / loop.ci_timeout_seconds halts and escalates. This is a cross-reference only — PR creation above is unchanged, and nothing extra runs when loop.ci_gate is false.

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. 9d ago First seen · 25 lines · 59 tokens per session scan A b4f6405036cc

Subscribe to this mod's changes

pr-azdo is a skill published in the GitHub repository chan4lk/specclaw (12 stars, last pushed 5d ago), licensed MIT. It adds 59 tokens to every session and 662 once invoked, about $0.0003 per session on Opus 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-30.

Related

Other skills, from other repositories

managing-github

Use when work reaches a GitHub-hosted issue, pull request or review, release, tag, or live deployment-branch boundary, including indirectly after investigation, completed development, or repository policy requires delivery. Also trigger when work discovers a repository defect that may need duplicate search or an issue…

rundesk-ai/rundesk-cli · 134 tokens

are-we-done

Deterministic close-out gate for a session or work tree. Sweeps a fixed set of sources — the todo list, this session's own promises, git state, TODO/FIXME markers the diff introduced, test and build state, and any issue or ticket referenced — and checks that every open point has been explicitly decided: done, won't…

adamlinscott/claude-skills · 199 tokens

ship-it

Get the work done in this conversation all the way out — merged, and deployed to every environment the repo has, production included. Grounds itself first in the branches written during this session, the open and closed PRs behind them, and the environments and CI/CD workflows the repo actually defines, then lands and…

adamlinscott/claude-skills · 134 tokens

pair

Dual-agent development workflow - Claude Code plans and reviews, Codex implements headlessly, git automated. ONLY runs when the user explicitly types /pair. NEVER activate automatically, no matter how well a task seems to match this workflow.

hyj28/claude-codex-pair · 48 tokens

ship-it-now

Same skill as /ship-it, with the ride-along confirmation gate turned off.

adamlinscott/claude-skills · 135 tokens

capture-lessons

Ship and capture lessons workflow. Creates the PR, updates lessons learned, updates documentation, generates the sprint retrospective, and updates the backlog. Use at the end of a sprint cycle, or when the user says "ship", "capture", "lessons", "retro", "retrospective", "wrap up", or "done with this sprint". Also use…

rbah31/claude-code-workflow · 100 tokens