Does this skill help with branch naming?

Yes, it enforces a specific format: / - or / to keep the repository organized.

What commit types are supported by these conventions?

It supports all standard Conventional Commit types including feat, fix, docs, chore, refactor, test, build, ci, perf, and style.

Why is there a focus on description accuracy?

The skill ensures descriptions reflect the final state of the code, removing mentions of discarded approaches or features to prevent reviewer confusion.

How does this skill determine the PR title?

The skill primarily analyzes the commit history to summarize the actual changes made, using the branch name only as a fallback hint for the initial intent.

What are the mandatory sections for a PR description?

Every PR description must include a Summary section (1-3 bullet points) and a Test Plan section detailing how to verify the changes.

Pull Request Conventions

Name: Pull Request Conventions
Author: zookanalytics

byzookanalytics

개발자 도구

Enforces standardized Git branch naming, PR titles, and documentation requirements to ensure consistent and high-quality pull request workflows.

소개

This skill provides a structured framework for managing the pull request lifecycle by implementing Conventional Commits and standardized branch naming patterns. It ensures that every PR includes an accurate summary and a verifiable test plan, while automating the derivation of PR titles from actual commit history rather than just branch names. By focusing on documentation accuracy and structural consistency, this skill helps teams maintain a clean git history and speeds up the code review process by eliminating ambiguity in PR descriptions.

주요 기능

Standardized branch naming patterns including feature, fix, and refactor types
Accuracy rules to ensure documentation reflects final code state
Conventional Commit-compliant PR title generation and validation
0 GitHub stars
Automated PR title derivation based on commit history analysis
Structured PR description templates with mandatory Summary and Test Plan sections

사용 사례

Ensuring squash-merge commit messages are descriptive and follow a structured schema
Standardizing PR formatting across distributed engineering teams to improve review speed
Automating the creation of accurate PR descriptions that reflect the final implementation

소개

주요 기능

Standardized branch naming patterns including feature, fix, and refactor types
Accuracy rules to ensure documentation reflects final code state
Conventional Commit-compliant PR title generation and validation
0 GitHub stars
Automated PR title derivation based on commit history analysis
Structured PR description templates with mandatory Summary and Test Plan sections

사용 사례

Ensuring squash-merge commit messages are descriptive and follow a structured schema
Standardizing PR formatting across distributed engineering teams to improve review speed
Automating the creation of accurate PR descriptions that reflect the final implementation