القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | create-pr-azdo |
| description | 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. |
| compatibility | Requires git, Azure CLI (az) with azure-devops extension, authentication, and network access. |
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).
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.
main branch.Before running any PR creation command, provide in chat:
## Problem
<why is this change needed?>
## Change
<what changed?>
## Verification
<how was it validated?>
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>
git branch --show-current
scripts/git-status.sh --short
git push -u origin HEAD
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
Minimum-requirements checklist for any change — code or docs-only. Run this before every PR creation or push to avoid CI failures on the first attempt.
Generate PNG screenshots for release notes using the repository's HtmlRenderer and ScreenshotGenerator tools. Use when asked to add screenshots to release notes or documentation.
Determine the next available issue number across all change types (feature, fix, workflow) by checking both local docs and remote branches, then reserve it by pushing an empty branch.
Convert the mermaid diagram in docs/agents.md to a blueprint-styled SVG for the website. Use when the workflow diagram in agents.md is updated and needs to be reflected on the website.
Run a focused accessibility pass for website changes (WCAG 2.1 AA-oriented).
Create and update interactive examples for the Eleventy website using page entrypoints and src/examples fragments.