skills.rest
werf
werfOFFICIAL
Explore all skills by this author →
Website𝕏@werf_ioGitHub

pull-request-name

Generate PR titles following werf conventions with a 72-character limit.

4.7k|237|Updated Jan 25, 2016
Search Tags:#git#code-review#pull-request#scopes#pr-workflow#pr-title#werf-conventions
One-click install
npx skills add https://github.com/werf/werf --skill pull-request-name
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-request-name
Source: https://github.com/werf/werf/tree/main/.agents/skills/pull-request-name
Command: npx skills add https://github.com/werf/werf --skill pull-request-name

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of PR titles that conform to werf conventions, reducing manual edits and review time.

Core Features & Use Cases

  • Enforces werf-conformant title format: <type>(<scope>): <subject>.
  • Handles nested scopes and ensures length limit of 72 characters.
  • Use Case: When opening PRs for features, fixes, or chores across components, the tool standardizes titles for consistent review.

Quick Start

Provide the PR type, scope, and subject to generate a conformant title.

Frequently Asked Questions about pull-request-name

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

FAQPage Schema
How do I format a pull request title to follow werf conventions?▼

To format a pull request title for werf conventions, use the structure <type>(<scope>): <subject>. This standardizes PR metadata across features, fixes, and chores to improve code review efficiency.

What is the character limit for a werf conformant PR title?▼

The character limit for a werf conformant PR title is 72 characters. Enforcing this length limit ensures consistent display across git platforms and keeps the subject concise for reviewers.

How do I generate a PR title for nested scopes in a git workflow?▼

To generate a PR title for nested scopes, provide the PR type, nested scope, and subject. The generation process automatically handles the nested structure while maintaining the <type>(<scope>): <subject> format.

Can I automate PR title generation for fixes and chores?▼

Yes, you can automate PR title generation for fixes and chores. Providing the specific PR type, scope, and subject allows the tool to output a conformant title, reducing manual edits during code review.

Why does my pull request title need a specific type and scope?▼

Your pull request title needs a specific type and scope to enforce werf conventions. Standardizing titles across features, fixes, and chores categorizes changes quickly, directly improving review workflow efficiency.

What is the best way to structure git PR titles for consistent code review?▼

The best way to structure git PR titles for consistent code review is applying the <type>(<scope>): <subject> format. Capping the total length at 72 characters further standardizes titles for automated processing.

Related Skills

Explore More Software Engineering Skills→
linkerdoglinkerdog
15

project-github-titles

Standardize GitHub commit and PR titles for the rara repository.

Official
Basic
tneztnez
2

pr

Creates a pull request from the current branch to main using GitHub CLI.

Community
Intermediate
randalmurphalrandalmurphal

Python Style Standards

Enforce Python style standards with ruff, pylint, and mypy.

Community
Advanced
windmill-labswindmill-labs
17.5k

pr

Create draft GitHub pull requests with conventional commit titles.

Official
Advanced