skills.rest
easingthemes
easingthemesCOMMUNITY
Explore all skills by this author →
Website𝕏@draganfillGitHub

dx-pr

Create a pull request via ADO MCP after validating all plan steps.

6|3|Updated Mar 21, 2026
Search Tags:#automation#git#workflow#mcp#ci-cd#ado#pull-request
One-click install
npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dx-pr
Source: https://github.com/easingthemes/dx-aem-flow/tree/main/plugins/dx-core/skills/dx-pr
Command: npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating a pull request after all plan steps are complete can be error-prone and time-consuming. This skill automates PR creation, ensuring all steps are finished, generating a PR description from share-plan.md, pushing the feature branch, and submitting the PR via ADO MCP tools.

Core Features & Use Cases

  • Validates that every step in implement.md is marked as done before PR creation.
  • Generates a PR description from share-plan.md, preserving ticket context.
  • Pushes the current branch and creates a PR via ADO MCP with proper base branch discovery and work item linking.
  • Supports hub mode to orchestrate PRs across multiple repositories when needed.
  • Aligns with governance rules (git-rules.md) to maintain consistency.

Quick Start

Run /dx-pr <Work Item ID> to create a PR after all plan steps are complete.

Frequently Asked Questions about dx-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull request creation after completing plan steps in Azure DevOps?▼

Automate pull request creation by validating all plan steps are done, generating PR descriptions from share-plan.md, pushing the branch, and submitting the PR via ADO MCP. This ensures no incomplete work is submitted.

How does ADO MCP handle work item linking when creating an automated PR?▼

ADO MCP auto-links the associated work item to the PR by reading project configuration and discovering the base branch dynamically, avoiding hardcoded branch names and maintaining ticket context.

Can I orchestrate PRs across multiple repositories in a single workflow?▼

Yes, multi-repo software development workflows are supported through hub mode, which orchestrates PR creation across multiple repositories after verifying all plan steps are complete.

What happens if not all steps in implement.md are marked as done?▼

PR creation is blocked until every step in implement.md is validated as complete. This prevents error-prone submissions and ensures all plan results are verified before pushing.

How is the PR description generated from share-plan.md?▼

The PR description is generated directly from share-plan.md content, preserving ticket context and aligning with governance rules in git-rules.md to maintain consistency across submissions.

Related Skills

Explore More Software Engineering Skills→
rom-orlovichrom-orlovich

planning

Generates a planning document with sequenced tasks and estimated durations from GitHub issues or other inputs, ready to be saved as PLAN.md in your repository.

Community
Intermediate
D0NMEGAD0NMEGA
8

gsd-ship

Push a branch, create a PR with an auto-generated body, and track merge status.

Community
Advanced
easingthemeseasingthemes
6

auto-webhooks

Configure ADO service hooks and PR policies from infra.json via REST API calls.

Community
Advanced
brandonalfredbrandonalfred
2

draft-pr

Create and push draft pull requests from GitHub feature branches.

Community
Intermediate