Generate conventional commit PR titles from git diff analysis.
npx skills add https://github.com/MetaMask/metamask-mobile --skill pr-title-metamask
Please help me install this Agent Skill. Skill: pr-title Source: https://github.com/MetaMask/metamask-mobile/tree/main/.agents/skills/pr-title Command: npx skills add https://github.com/MetaMask/metamask-mobile --skill pr-title-metamask
This Skill automates the creation of PR titles that conform to the conventional commit style, reducing manual drafting time and ensuring consistency.
Provide the current branch or diff output and ask the AI to generate a conventional PR title.
High-intent search queries and answers about installing and using this skill.
To generate a conventional commit PR title, provide your branch's git diff to the tool, which analyzes code changes and outputs a formatted title following the conventional commits structure.
The conventional commit format for PR titles requires a type, an optional scope, and a description (e.g., type[optional scope]: description). The type and scope must be lowercase, use imperative mood, and stay under 72 characters.
Writing a PR title in imperative mood from code changes involves analyzing the git diff to determine the change type, then structuring the description as a direct command such as add, fix, or refactor.
Yes, the conventional PR title generator enforces a strict maximum length of 72 characters to ensure repository history remains clean and readable across different Git platforms.
Yes, you can automate PR title creation for feature and refactor branches by passing the git diff output to the tool, which identifies the change type and generates the appropriate conventional commit title.
Pull request titles fail conventional commit checks when they exceed 72 characters, use incorrect capitalization, lack a valid type, or miss the imperative mood structure required by standard Git workflow linters.
windmill-labsCreate draft GitHub pull requests with conventional commit titles.
yamato0811Summarize Git branch diffs and draft a pull request targeting develop.
shellicarValidate Git commit messages, staging practices, and push commands.
zhengfranGenerate Conventional Commit messages in the type(scope): description format.
