skills.rest
ducthang-hub
ducthang-hubCOMMUNITY
Explore all skills by this author →
GitHub

raise-pull-request-ai-kit

Create or update Azure DevOps pull requests with Jira status synchronization.

Updated May 11, 2026
Search Tags:#pull request#azure devops#git push#jira integration#pr description#mcp ado repo#workflow transition
One-click install
npx skills add https://github.com/ducthang-hub/nw-ai-kit --skill raise-pull-request-ai-kit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: raise-pull-request-ai-kit
Source: https://github.com/ducthang-hub/nw-ai-kit/tree/main/.agents/skills/raise-pull-request-ai-kit
Command: npx skills add https://github.com/ducthang-hub/nw-ai-kit --skill raise-pull-request-ai-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating or updating Azure DevOps pull requests by ensuring your branch is pushed, your Jira card status is fetched (and transitioned when appropriate), and the PR description accurately reflects the final git diff.

Core Features & Use Cases

  • Checks for readiness to raise/update a PR: Verifies git status, ensures there are commits to push, and prevents creating PRs with no new content.
  • Creates or updates PRs safely: Detects whether an active PR already exists for the current branch and updates the PR description instead of duplicating work.
  • Synchronizes Jira workflow state: Extracts the Jira key from the branch name, fetches the current Jira status, applies transitions toward “In Development” / “In Progress” when valid, and records the confirmed final status in the PR.
  • Generates PR metadata from real changes: Uses repository default branch from Azure DevOps and bases the “Changes” list on net git diff (final differences), not intermediate commits.

Quick Start

Ask the AI to use raise-pull-request-ai-kit to create or update a pull request for my current branch in Azure DevOps, ensuring the Jira card status is fetched and the PR description matches the final git diff.

Frequently Asked Questions about raise-pull-request-ai-kit

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

FAQPage Schema
How do I create an Azure DevOps pull request that automatically updates my Jira card status?▼

To create an Azure DevOps pull request with automatic Jira status updates, the workflow extracts the Jira key from your branch name, fetches the issue status, applies valid transitions toward In Progress, and records the final status in the PR description. This ensures your Jira card state remains synchronized with your code changes.

How do I update an existing Azure DevOps PR description after pushing new commits?▼

Updating an existing Azure DevOps PR after new commits involves detecting the active PR for your current branch and regenerating the PR description from the final net git diff. This prevents duplicate pull requests and ensures the changes list accurately reflects the cumulative differences rather than intermediate commits.

Does the PR creation workflow require a git push before raising a pull request in Azure DevOps?▼

Yes, a git push is required before raising a pull request in Azure DevOps. The workflow verifies git status, ensures there are commits to push, and prevents creating PRs with no new content. It also handles cases with uncommitted changes or no commits to push by validating branch readiness first.

Can I use Jira-driven branch naming to automatically link pull requests to Jira issues?▼

Yes, you can use Jira-driven branch naming formats like JIRA-NUMBER-description to automatically link pull requests to Jira issues. The workflow extracts the Jira key from the branch name, fetches the issue via Jira integration, and applies workflow transitions before composing the PR description.

How does the PR description reflect the actual code changes in my Azure DevOps repository?▼

The PR description reflects actual code changes by using the repository default branch from Azure DevOps and basing the changes list on the final net git diff. This approach captures the ultimate differences between your branch and the default branch, providing an accurate summary of all modifications.

What happens if there are no new commits to push when creating a pull request in Azure DevOps?▼

If there are no new commits to push, the workflow prevents creating a pull request to avoid empty PRs. It checks for readiness by verifying git status and ensuring there is new content to push, handling cases with uncommitted changes or no commits before attempting any PR operations in Azure DevOps.

Related Skills

Explore More Software Engineering Skills→
TMI-appsTMI-apps
2

push

Validate and push committed Git changes to a remote repository.

Official
Intermediate
avvaleavvale

commit-pr

Commit changes, push to a feature branch, and create a GitHub Pull Request.

Official
Advanced
bakwankawabakwankawa

jira

Manage Jira issues via natural language across CLI or MCP backends.

Community
Advanced
encero-systemsencero-systems
92

create-pr-description

Generate PR descriptions from repository templates and git diff changes.

Official
Intermediate