Verified:GitHub

pr-creator

Create pull requests across ADO, GitLab, GitHub, and Jira with branch validation and work-item linking.

11|4|Updated Apr 27, 2026

Search Tags:#automation #git #branching #pr #code-review #pull-request #work-item

One-click install

npx skills add https://github.com/MostAshraf/ai-sdlc-harness --skill pr-creator-mostashraf

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: pr-creator
Source: https://github.com/MostAshraf/ai-sdlc-harness/tree/main/skills/pr-creator
Command: npx skills add https://github.com/MostAshraf/ai-sdlc-harness --skill pr-creator-mostashraf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a Pull Request (or Merge Request) after all tasks and tests are approved. Assembles PR summary from the task tracker, validates branch naming, and creates the PR/MR via the configured git provider. Links back to the work item via the work item provider. Supports ADO, GitLab, GitHub, and Jira. Used during Phase 6 of the workflow.

Core Features & Use Cases

Provider-agnostic PR creation: Assemble and submit PRs across ADO, GitLab, GitHub, and Jira using a unified interface.
Branch validation & linking: Enforces naming conventions and links the PR to the originating work item.
End-to-end workflow support: Works across multi-repo or single-repo contexts, with automatic tracker linking and provider adapters.

Quick Start

Run the pr-creator with a Work-Item-ID, team name, and optional repo name to generate and create the PR.

Frequently Asked Questions about pr-creator

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

FAQPage Schema

How do I automate pull request creation across multiple git providers?▼

Automated pull request creation across multiple git providers is achieved by assembling PR details from a work item, validating branch naming conventions, and submitting the PR via a unified provider adapter interface.

Can I link a pull request to a work item in Jira or Azure DevOps?▼

Linking a pull request to a work item in Jira or Azure DevOps is supported by automatically updating the task tracker with the newly created PR details using configured work item provider adapters.

Does unified PR creation work for multi-repo scenarios?▼

Unified PR creation works for both single-repo and multi-repo scenarios by defining the pull request scope and work item linking using work item IDs, team names, and optional repository names.

What is the best way to ensure branch naming validation before creating a pull request?▼

Ensuring branch naming validation before creating a pull request involves running pre-flight checks that enforce standard naming conventions and assemble the PR summary directly from the task tracker.

Which git platforms are supported for automated merge request generation?▼

Automated merge request generation is supported across Azure DevOps, GitLab, GitHub, and Jira, allowing provider-agnostic submission and tracking through standard provider adapters.

Do I need a work item ID to generate a pull request summary?▼

A work item ID is required to generate a pull request summary, as it defines the PR scope, enables branch validation, and links the resulting pull request back to the originating task tracker.