h-pr-submission

Name: h-pr-submission
Availability: InStock
Author: mituso89

Guide Git to pull request workflow with commit standards and Azure DevOps integration.

2|Updated Jul 2, 2026

Search Tags:#quality assurance #pull request #git workflow #code contribution #ADO integration

Ready to run

npx skills add https://github.com/mituso89/Spec-Driven-Development-toolkits --skill h-pr-submission

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: h-pr-submission
Source: https://github.com/mituso89/Spec-Driven-Development-toolkits/tree/main/elay/h-pr-submission
Command: npx skills add https://github.com/mituso89/Spec-Driven-Development-toolkits --skill h-pr-submission

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, Azure DevOps, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the complex process of submitting code contributions by guiding users through all steps from commit messages to pull request creation, ensuring quality, adherence to standards, and user approval.

Core Features & Use Cases

Commit Message Standards: Enforces Conventional Commits for clear commit messages.
Branch Naming Convention: Automates branch naming to standardize workflow.
Quality Gates: Requires code health and quality checks before submitting.
User Approval: Ensures code changes are reviewed and approved before commit.
ADO Story Integration: Integrates with Azure DevOps for story tracking and labeling.

Quick Start

Use the h-pr-submission skill to submit a PR following the Git to PR workflow: Run 'h-pr-submission' after completing all coding tasks.

Frequently Asked Questions about h-pr-submission

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

FAQPage Schema

How do I enforce conventional commit messages and branch naming in my Git workflow?▼

To enforce conventional commit messages and standardize branch naming in your Git workflow, this guided process automates naming conventions and validates commit formats before submission. This ensures consistent and high-quality code contributions across your repository.

How do I run mandatory quality checks before creating a pull request?▼

Mandatory quality checks before creating a pull request are executed through built-in quality gates that verify code health. The workflow requires these checks to pass and demands explicit user approval before allowing any code commit.

Does this pull request workflow integrate with Azure DevOps for story tracking?▼

Yes, this pull request workflow integrates directly with Azure DevOps for story tracking and labeling. It automatically associates your Git code contributions with the corresponding ADO stories to maintain project alignment.

What is the best way to standardize code contributions for pull requests?▼

The best way to standardize code contributions is using a guided Git to Pull Request workflow that enforces commit standards, automates branch naming, and mandates quality gates. This approach guarantees consistent, high-quality submissions.

Do I need Git and Azure DevOps to use this code contribution workflow?▼

Yes, you need both Git and Azure DevOps configured to use this code contribution workflow. The process relies on Git for branch and commit management and Azure DevOps for story integration, tracking, and labeling.