ado-pr-create
Skill0 starsChanged 6 months agoMITView on GitHub
Create a draft pull request in Azure DevOps for the bug fixes — sets the required reviewer, optional reviewers, and links work items in a single command. Owns the PR description format and the reviewer table. Use when the user says "open the PR", "create draft PR", "ship the bugs", or when the orchestrator finishes the reviewer step.
- Reads credentials
- Commits and pushes
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ado-bug-lifecycleSkill
- ado-bug-querySkill
- bug-captureSkill
- bug-reviewer-runSkill
- bug-triage-sessionSkill
- storyblok-bugfix-storySkill
- storyblok-component-pushSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
No AI references in commits
- Distinctive: line 51
Keep it short — ADO has a 4000-character limit and a batch of 12+ bugs hits it fast.
- Very specific: line 84
If your team uses GUIDs instead of emails for some flows (e.g.
- Very specific: line 90
Always
--draft: Never open a non-draft PR from this flow.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Azure DevOps — Draft PR Creation
One-shot PR creation. All reviewers and work items are set at creation time — no follow-up commands needed.
Prerequisites
- Branch is pushed to origin:
git push -u origin <branch-name> - Reviewer has approved every bug in
results.json(no"status": "feedback"outstanding) - Type-checking passes (ignore pre-existing errors)
- No AI references in commits
Single command — create the PR
Reviewers come from .env:
$YOUR_REQUIRED_REVIEWER_EMAIL— set as required at PR creation$YOUR_REVIEWER_1_EMAIL,$YOUR_REVIEWER_2_EMAIL— added as optional reviewers
az repos pr create \
--title "<short title under 70 chars>" \
--description "$(cat <<'EOF'
<see PR description format below>
EOF
)" \
--draft \
--source-branch <branch-name> \
--target-branch dev \
--work-items <ID1> <ID2> ... \
--required-reviewers "$YOUR_REQUIRED_REVIEWER_EMAIL" \
--reviewers "$YOUR_REVIEWER_1_EMAIL" "$YOUR_REVIEWER_2_EMAIL"--required-reviewers and --work-items work at creation. Do not chain follow-up az repos pr reviewer add or az repos pr work-item add — the create command handles both.
az repos pr reviewer add does not have a --required flag.
PR description format
Keep it short — ADO has a 4000-character limit and a batch of 12+ bugs hits it fast.
## Bug Fixes
| # | Bug | Fix |
|---|-----|-----|
| [12345](https://dev.azure.com/<YOUR_AZURE_ORG>/<YOUR_AZURE_PROJECT>/_workitems/edit/12345) | Header alignment off on mobile | Constrained container to `max-w-screen-md` |
| [12346](https://dev.azure.com/<YOUR_AZURE_ORG>/<YOUR_AZURE_PROJECT>/_workitems/edit/12346) | Icon weight inconsistent | Updated to `weight="regular"` consistently |
## Remaining Bugs (not in this PR)
**Medium:**
- 12347 — Title — reason it's medium
**Hard:**
- 12348 — Title — reason it's hardADO work item URL pattern: $AZURE_ORG/$AZURE_PROJECT/_workitems/edit/<ID>
Reviewer reference
The reviewers below are an example layout — configure your own in .env as YOUR_REQUIRED_REVIEWER_EMAIL, YOUR_REVIEWER_1_EMAIL, YOUR_REVIEWER_2_EMAIL.
| Reviewer | Env var | Role |
| Tech Lead (required) | $YOUR_REQUIRED_REVIEWER_EMAIL | Required at PR creation |
| Reviewer 1 | $YOUR_REVIEWER_1_EMAIL | Optional |
| Reviewer 2 | $YOUR_REVIEWER_2_EMAIL | Optional |
If your team uses GUIDs instead of emails for some flows (e.g. ADO REST API), look up the GUID once with az devops user show --user <email> and store it alongside the email in .env (e.g. YOUR_REQUIRED_REVIEWER_ID). The az repos pr create flags accept email — GUIDs are only needed for direct REST calls.
Hard rules
- Always
--draft. Never open a non-draft PR from this flow. - Target branch is
dev(or whatever your team's integration branch is). Nevermainormasterdirectly from this flow. - No AI references in title or description.
- Set required reviewer at creation — there's no clean way to make it required afterwards via CLI.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

