pr-workflow

Create pull requests with standardized titles and bodies from Git outputs.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/verivend/verivend-vue3-template --skill pr-workflow-verivend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-workflow
Source: https://github.com/verivend/verivend-vue3-template/tree/main/.claude/skills/pr-workflow
Command: npx skills add https://github.com/verivend/verivend-vue3-template --skill pr-workflow-verivend

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill standardizes the process of creating pull requests, ensuring consistency in titles, descriptions, and pre-merge quality checks, thereby improving code review efficiency and maintainability.

Core Features & Use Cases

  • Standardized PR Titles: Enforces a type(scope): description format for clarity.
  • Automated Quality Checks: Integrates linting, type checking, and unit tests before PR creation.
  • Contextual PR Body Generation: Derives PR descriptions directly from git log and git diff to prevent hallucinations.
  • Use Case: When you've finished a feature branch, use this Skill to automatically generate a well-formatted PR title and body based on your commits and staged changes, along with running all necessary pre-checks.

Quick Start

Use the pr-workflow skill to create a new pull request for your current branch.

Frequently Asked Questions about pr-workflow

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

FAQPage Schema
How do I automate pull request creation with standardized titles and descriptions?

Automate pull request creation by deriving standardized titles and descriptions directly from git commit and diff outputs, enforcing a type(scope): description format for consistency. This standardizes PR generation and improves code review efficiency.

How do I generate a pull request body from git commits without hallucinations?

Generate pull request bodies from git commits by extracting contextual information directly from git log and git diff outputs. Deriving descriptions from actual staged changes prevents hallucinations and ensures accurate code review documentation.

Can I enforce linting, type checking, and unit tests before creating a pull request?

You can enforce linting, type checking, and unit tests before pull request creation through automated pre-checks. Integrating these quality checks ensures code conventions are maintained and prevents unreviewed errors from entering the codebase.

What is the best way to standardize code review processes for a software development team?

Standardize code review processes by automating pull request creation with formatted titles, contextual bodies from git diffs, and mandatory quality pre-checks. This enforces project conventions and maintains consistent code quality across the team.

Does this pull request automation work with my existing GitHub and CI/CD workflows?

Pull request automation integrates with GitHub and CI/CD workflows by executing pre-checks like linting and unit tests before PR creation. It leverages git commit and diff outputs to generate standardized titles and bodies for code review.

Why should I use automated PR generation instead of manually writing pull request descriptions?

Automated PR generation eliminates manual description writing by deriving standardized titles and contextual bodies directly from git log and diff outputs. This enforces project conventions, reduces human error, and streamlines the code review process.