update-pr-title

Update GitHub Pull Request titles to Conventional Commits format.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/howarewoo/monorepo-template --skill update-pr-title
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-pr-title
Source: https://github.com/howarewoo/monorepo-template/tree/main/.claude/skills/update-pr-title
Command: npx skills add https://github.com/howarewoo/monorepo-template --skill update-pr-title

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of titling your Pull Requests, ensuring they adhere to the Conventional Commits specification for better project organization and automated changelog generation.

Core Features & Use Cases

  • Automated Title Generation: Analyzes code changes to suggest and apply titles in type(scope): description format.
  • Conventional Commits: Enforces a standardized format for commit messages, improving clarity and enabling automated tooling.
  • Use Case: After pushing changes to a feature branch, invoke this Skill to automatically update the PR title from a generic name to a descriptive one like feat(api): implement user authentication endpoint.

Quick Start

Run the update-pr-title skill to automatically set the title for the current pull request.

Frequently Asked Questions about update-pr-title

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

FAQPage Schema
How do I automatically format a GitHub pull request title to follow Conventional Commits?

To automatically format a GitHub pull request title for Conventional Commits, you can use an automation tool that analyzes code diffs to determine the commit type and scope, then generates and applies a descriptive title.

What is the best way to generate a Conventional Commits PR title from code changes?

The best way to generate a Conventional Commits PR title from code changes is to analyze the code diffs to identify the appropriate commit type (such as feat or fix) and scope, then synthesize this data into a descriptive title.

Can I update the title of a specific pull request instead of the current one?

Yes, you can update the title of a specific pull request by specifying the PR number, allowing the automation to target and update that exact pull request title instead of the current active branch.

How does analyzing code diffs determine the correct commit type for a pull request?

Analyzing code diffs determines the correct commit type by examining the modifications to infer the intent of the changes, categorizing them into types like feat, fix, or refactor to construct a compliant Conventional Commits title.

Do I need to manually specify the commit type and scope for my PR title automation?

No, you do not need to manually specify the commit type and scope, because the automation analyzes the code diffs directly to determine the appropriate Conventional Commits category and scope automatically.