skills.rest
miltonparedes
miltonparedesCOMMUNITY
Explore all skills by this author →
GitHub

pr-title

Generate and assign semantic PR titles for squash-merge workflows.

Updated Feb 7, 2026
Search Tags:#automation#workflow#pr#semantic#pull-request#title
One-click install
npx skills add https://github.com/miltonparedes/agentfiles --skill pr-title-miltonparedes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-title
Source: https://github.com/miltonparedes/agentfiles/tree/main/skills/pr-title
Command: npx skills add https://github.com/miltonparedes/agentfiles --skill pr-title-miltonparedes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate and update PR/MR titles to follow semantic-commit style for squash-merge workflows, reducing friction and improving changelog clarity.

Core Features & Use Cases

  • Infer PR titles from branch names and changes.
  • Propose 2-3 title options and apply via gh pr edit or glab mr update.
  • Works with feature/ fix/ refactor branch patterns and user prompts to rename existing PR titles.

Quick Start

Tell the AI to set a PR title by providing a short description of the change.

Frequently Asked Questions about pr-title

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

FAQPage Schema
How do I set semantic PR titles consistently for squash merges?▼

You can set semantic PR titles for squash merges by providing a short description of the change, allowing the tool to infer and apply the title via gh pr edit or glab mr update.

Can I generate a pull request title automatically from a branch name?▼

Yes, PR titles can be generated from branch names by recognizing feat, fix, refactor, and chore patterns to propose 2-3 semantic title options for your workflow.

Does this workflow support both GitHub and GitLab merge requests?▼

Yes, the workflow supports both GitHub and GitLab by applying semantic titles through gh pr edit --title for pull requests and glab mr update for merge requests.

What is the best way to rename an existing PR title to follow semantic commit style?▼

The best way to rename an existing PR title to semantic commit style is to prompt the tool with your requested change, which then updates it directly using gh pr edit or glab mr update.

Why use semantic PR titles for squash-merge workflows?▼

Semantic PR titles are used for squash-merge workflows to reduce manual friction and improve changelog clarity by ensuring merged commit messages follow a consistent naming convention.

Related Skills

Explore More Software Engineering Skills→
gufrancogufranco
11

pr

Automates pull request creation and updates across GitHub and GitLab using gh or glab CLI tools.

Community
Advanced
zinohomezinohome
1

changelog-writer

Generate changelogs and release notes from git commits, PR titles, and issue references.

Community
Intermediate
droidconKEdroidconKE
8

commit-convention

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

Official
Basic
BSteffaniakBSteffaniak

commit-message

Generate a git commit message with title and description for current changes.

Community
Basic