OpenParable
Skip to content
← Back to skills

Pull Request Name

Productivity
pull-request-name

Pull Request Name is an Agent Skill for productivity published in the werf/werf repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Generates Pull Request titles and descriptions according to werf conventions. Use when creating or updating a PR.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/werf/werf/blob/HEAD/.agents/skills/pull-request-name/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/pull-request-name, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Pull Request Conventions

Defaults

  • Always create PRs as draft (gh pr create --draft). The author marks it ready for review manually.

Title

  1. Read types, scopes, and formatting rules from CONTRIBUTING.md#conventions.
  2. The PR title should mirror the header of the main commit in the PR.
  3. Format the title as <type>(<scope>): <subject>.
  4. Keep the total length ≤ 72 characters.
  5. Nested scopes are allowed and encouraged.

Description

Use the following structure. Every section is mandatory — omit a section only when it genuinely does not apply (e.g. single-line typo fix may skip Review focus / risks).

## Summary

<1-3 sentence high-level overview of what the PR does and why it exists.>

## Key changes

- <concrete change 1>
- <concrete change 2>
- …

## Why

<Motivation: what problem this solves, what maintenance/UX/perf gain it brings.>

## Review focus / risks

- <area or file that deserves careful review>
- <potential risk or side-effect>

Rules

  • Language: match the project's primary language (English by default).
  • Be specific: name files, modules, functions — not "updated some code".
  • Key changes: group related items; use sub-bullets for detail when helpful.
  • Why: explain the reason, not what changed (that's Key changes).
  • Review focus / risks: guide the reviewer — call out non-obvious consequences, large generated diffs, breaking changes.
  • No AI-slop filler ("This PR improves the codebase…"). Every sentence must carry information.

Output

When generating only the title (e.g. for gh pr edit --title), output ONLY the title, with no additional text, quotes, or formatting.