pr

Generate GitHub pull requests with conventional commit titles and PR Description Templates.

Updated Nov 30, 2023
One-click install
npx skills add https://github.com/deanmoses/tacocat-gallery-hosting-aws --skill pr-deanmoses
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/deanmoses/tacocat-gallery-hosting-aws/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/deanmoses/tacocat-gallery-hosting-aws --skill pr-deanmoses

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures pull requests follow conventional commit formatting and standardized templates, reducing review time and miscommunication across teams.

Core Features & Use Cases

  • Enforce conventional commit formatting on PR titles
  • Provide a PR Description Template and guidance on labels, as well as branch naming conventions
  • Support common PR workflows including features, fixes, docs, and refactors

Quick Start

Create a PR with the title 'feat(auth): add login flow' and fill the description using the PR Description Template provided in this skill.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I enforce conventional commits on GitHub pull request titles?

To enforce conventional commits on GitHub pull request titles, use this skill to automatically validate and generate PR metadata. It standardizes PR titles like 'feat(auth): add login flow' to reduce review time and team miscommunication.

What is the standard format for a pull request description template?

A standard pull request description template provides structured sections for features, fixes, docs, and refactors. This skill supplies a PR Description Template and guidance on labels and branch naming conventions to ensure consistent PR workflows.

How do I create a pull request with conventional commit formatting?

To create a pull request with conventional commit formatting, start with a title like 'feat(auth): add login flow' and fill the description using the provided PR Description Template. This relies on standard GitHub workflows for generating consistent PR metadata.

Does this PR standardization skill support documentation updates and code refactors?

Yes, this PR standardization skill supports common software project workflows including documentation updates, code refactors, feature submissions, and bugfixes. It applies conventional commit formatting and standardized templates across all these pull request types.

Do I need external dependencies to standardize branch naming conventions for pull requests?

No external dependencies are required to standardize branch naming conventions for pull requests. This skill operates independently, relying on standard GitHub workflows and internal templates to enforce naming conventions and generate consistent PR metadata.