pull-request

Analyze branch changes and generate compliant pull request titles and bodies.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/MayMustAI/ai-dev-playbook --skill pull-request-maymustai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/MayMustAI/ai-dev-playbook/tree/main/plugins/maymust/skills/pull-request
Command: npx skills add https://github.com/MayMustAI/ai-dev-playbook --skill pull-request-maymustai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating PRs manually can be error-prone and inconsistent. This skill automates generating PR titles that follow team conventions and crafting concise, structured PR bodies that cater to both human and AI reviewers, all while enforcing a guided verification loop.

Core Features & Use Cases

  • Analyzes branch changes to derive a representative PR title matching the commit conventions.
  • Proposes a structured PR body designed for the dual-audience review workflow (human + AI reviewer).
  • Enforces a five-step interactive verification loop to confirm intent and changes before submission.

Quick Start

Ask your AI to create a PR by analyzing the current branch, producing a compliant title and optimized body, then proceed with gh pr create.

Frequently Asked Questions about pull-request

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

FAQPage Schema
How do I automate GitHub pull request creation with consistent titles and structured bodies?

Automating GitHub pull request creation involves analyzing branch changes to derive a convention-compliant title and an optimized body, then executing gh pr create. This enforces a five-step interactive verification loop to confirm changes before submission.

What is the best way to generate pull request bodies for both human and AI code review workflows?

Generating pull request bodies for AI-human review workflows requires structuring the content to serve dual audiences. The skill proposes a structured PR body designed specifically for both human reviewers and AI reviewers to process code changes efficiently.

How do I ensure my pull request title matches team commit conventions before running gh pr create?

Ensuring a pull request title matches commit conventions requires analyzing branch changes to automatically derive a representative title. The generated title follows established team commit conventions before proceeding with the gh pr create command.

Does the pull request automation workflow require any specific GitHub dependencies or components?

The pull request automation workflow requires no specific dependencies or components. It operates independently, needing only the gh pr create command to function and enforce its interactive verification loop for quality assurance.

Why does AI-assisted PR generation need an interactive verification loop before submission?

AI-assisted PR generation needs an interactive verification loop to prevent error-prone submissions and enforce quality control. The five-step loop confirms user intent and validates changes before the pull request is officially created on GitHub.

When do I need a guided verification loop for automated pull request workflows?

A guided verification loop for automated pull request workflows is needed when team PR workflows require consistent commit message styles and a strict AI-human review loop for each change set to maintain quality standards.