skills.rest
zookanalytics
zookanalyticsOFFICIAL
Explore all skills by this author →
GitHub

pull-request-conventions

Enforce branch naming, PR title, and description conventions for Git workflows.

Updated Dec 10, 2025
Search Tags:#pr#code-review#git-workflow#pull-request#conventional-commits#branch-naming#workflow-management
One-click install
npx skills add https://github.com/zookanalytics/claude-devcontainer --skill pull-request-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-request-conventions
Source: https://github.com/zookanalytics/claude-devcontainer/tree/main/packages/git-workflow/skills/pull-request-conventions
Command: npx skills add https://github.com/zookanalytics/claude-devcontainer --skill pull-request-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes pull request practices by enforcing branch naming, PR title formats, and description requirements.

Core Features & Use Cases

  • Branch naming conventions: enforce a predictable <type>/<issue-number>-<description> or <type>/<description> pattern aligned with conventional commit types.
  • PR title and description rules: ensure titles follow Conventional Commits and include a clear, descriptive summary for review and history.
  • Guidance for deriving PR titles: provide a process to map commits to accurate titles and descriptions for downstream merges.

Quick Start

Start a PR by using the prescribed branch naming and PR title/description formats.

Frequently Asked Questions about pull-request-conventions

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

FAQPage Schema
How do I standardize pull request titles and branch naming conventions?▼

You can standardize pull request titles and branch naming by enforcing a <type>/<description> pattern for branches and Conventional Commits formats for PR titles to ensure consistent review history.

What is the best way to map git commits to a PR title and description?▼

Mapping git commits to a PR title involves deriving a Conventional Commits-style title from your branch type and structuring the PR description to provide a clear summary for downstream code reviews and merges.

How do I enforce conventional commits in pull request workflows?▼

Enforcing conventional commits in pull request workflows requires setting PR title rules that mandate specific commit types and pairing them with a structured description format for code review.

Do I need a specific branch naming format for feature branches and bug fixes?▼

Yes, using a predictable branch naming format like <type>/<issue-number>-<description> for feature branches and bug fixes aligns your workflow with conventional commit types and standardizes PR generation.

Can I use structured PR description rules for git workflow management?▼

Yes, applying structured PR description rules during git workflow management ensures that every pull request includes a descriptive summary, which clarifies the code review process and maintains review history.

Related Skills

Explore More Software Engineering Skills→
mindfu23mindfu23
3

crew-commit

Automate Git workflow with pre-commit checks, branch creation, and pull request generation.

Community
Intermediate
jefflesterjefflester
41

git-workflow

Standardize Git workflows with Conventional Commits and branch naming.

Community
Basic
nathanperkinsnathanperkins

prepare-commit

Guide code review, run formatting and linting checks, and suggest conventional commit messages.

Community
Intermediate
droidconKEdroidconKE
8

commit-convention

Generate commit subjects, branch names, and PR titles following Chai's conventions.

Official
Basic