How do I install the Create Pr Azdo skill?

Run npx skillmds add majiayu000/create-pr-azdo in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Create Pr Azdo safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Create Pr Azdo?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Create Pr Azdo free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Create Pr Azdo?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Create Pr Azdo by majiayu000 — Agent Skill

Name: Create Pr Azdo
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

File contents

Create PR (Azure DevOps)

Purpose

Create an Azure DevOps pull request in a consistent way, while still encoding the repository’s preference for a linear history.

This skill prefers using the repo wrapper script scripts/pr-azdo.sh to minimize Maintainer approval interruptions (single terminal invocation).

Notes on Merge Policy

CONTRIBUTING.md specifies Rebase and merge as the required merge strategy for this repo.

Azure DevOps UI/merge options differ by project settings. When merging an Azure DevOps PR, choose the most “rebase/linear-history” option available (often called Rebase and fast-forward) when available; otherwise, ask the Maintainer what to use.

Hard Rules

Must

Work on a non-main branch.
Ensure the working tree is clean before creating a PR.
Push the branch before creating the PR.
Keep PR title and description conventional and review-friendly.
Before creating the PR, post the exact Title and Description in chat.
Use the standard description template (Problem / Change / Verification).

Must Not

Merge using a strategy that introduces merge commits unless the Maintainer explicitly requests it.

Actions

0. Title + Description (Required)

Before running any PR creation command, provide in chat:

PR title (exact)
PR description (exact), using this template:

## Problem
<why is this change needed?>

## Change
<what changed?>

## Verification
<how was it validated?>

Recommended: One-Command Wrapper

scripts/pr-azdo.sh create --title "<type(scope): summary>" --description "<why + what + testing notes>"

Abandon a test PR (cleanup):

scripts/pr-azdo.sh abandon --id <pr-id>

1. Pre-flight Checks

git branch --show-current
git status --short

2. Push the Branch

git push -u origin HEAD

3. Create the PR

This is a minimal example; set --organization/--project appropriately for the target repo.

az repos pr create \
  --title "<type(scope): summary>" \
  --description "<why + what + testing notes>" \
  --source-branch "$(git branch --show-current)" \
  --target-branch main

4. Merging

If you need to merge the PR, confirm the exact merge option with the Maintainer first.
Prefer a rebase/linear-history option when available.

---name: create-pr-azdodescription: Create an Azure DevOps pull request using az devops tooling; include the repo’s linear-history merge preference and ask the Maintainer if merge options differ.--- # Create PR (Azure DevOps) ## Purpose Create an Azure DevOps pull request in a consistent way, while still encoding the repository’s preference for a **linear history**. This skill prefers using the repo wrapper script `scripts/pr-azdo.sh` to minimize Maintainer approval interruptions (single terminal invocation). ## Notes on Merge Policy `CONTRIBUTING.md` specifies **Rebase and merge** as the required merge strategy for this repo. Azure DevOps UI/merge options differ by project settings. When merging an Azure DevOps PR, choose the most “rebase/linear-history” option available (often called **Rebase and fast-forward**) when available; otherwise, ask the Maintainer what to use. ## Hard Rules ### Must - Work on a non-`main` branch. - Ensure the working tree is clean before creating a PR. - Push the branch before creating the PR. - Keep PR title and description conventional and review-friendly. - Before creating the PR, post the **exact Title and Description** in chat. - Use the standard description template (Problem / Change / Verification). ### Must Not - Merge using a strategy that introduces merge commits unless the Maintainer explicitly requests it. ## Actions ### 0. Title + Description (Required) Before running any PR creation command, provide in chat: - **PR title** (exact) - **PR description** (exact), using this template: ```markdown ## Problem <why is this change needed?> ## Change <what changed?> ## Verification <how was it validated?> ``` ### Recommended: One-Command Wrapper ```bash scripts/pr-azdo.sh create --title "<type(scope): summary>" --description "<why + what + testing notes>" ``` Abandon a test PR (cleanup): ```bash scripts/pr-azdo.sh abandon --id <pr-id> ``` ### 1. Pre-flight Checks ```bash git branch --show-current git status --short ``` ### 2. Push the Branch ```bash git push -u origin HEAD ``` ### 3. Create the PR This is a minimal example; set `--organization`/`--project` appropriately for the target repo. ```bash az repos pr create \ --title "<type(scope): summary>" \ --description "<why + what + testing notes>" \ --source-branch "$(git branch --show-current)" \ --target-branch main ``` ### 4. Merging - If you need to merge the PR, confirm the exact merge option with the Maintainer first. - Prefer a rebase/linear-history option when available.

Frequently asked questions