pr-title
Generate a conventional commit PR title from git diff analysis. Use when the user asks to generate a PR title, write a pull request title, or create a conventional commit title for a branch.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted description that clearly communicates its purpose and includes explicit trigger guidance. It excels in completeness and distinctiveness, with good natural trigger terms. The only minor weakness is that it describes a single action rather than elaborating on specific sub-capabilities (e.g., analyzing diffs, choosing commit type prefixes, formatting).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (PR titles, conventional commits) and the core action (generate a title from git diff analysis), but only describes a single action rather than listing multiple concrete capabilities. | 2 / 3 |
Completeness | Clearly answers both 'what' (generate a conventional commit PR title from git diff analysis) and 'when' (explicit 'Use when...' clause listing specific trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would actually say: 'PR title', 'pull request title', 'conventional commit title', 'branch', and 'generate'. These cover the most common phrasings a user would use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — PR title generation using conventional commit format from git diffs. Unlikely to conflict with general git, commit message, or code review skills due to the precise focus on PR titles and conventional commit format. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that provides clear, actionable guidance for generating conventional commit PR titles. The type table, scope guidance, and extensive examples make it immediately useful. The only notable gap is the lack of a pre-submission validation step in the workflow (e.g., checking character count or format compliance before the PR is created).
Suggestions
Add a validation step in the workflow, e.g., 'Verify the title is ≤72 characters and matches the pattern `^(feat|fix|refactor|chore|test|docs|perf|style|ci|build|revert)(\(.+\))?: .+$`' before outputting the final title.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured. The type table is an efficient reference format, and there's no unnecessary explanation of what conventional commits are or how git works. Every section earns its place. | 3 / 3 |
Actionability | Provides concrete git commands, a complete type reference table, specific formatting rules (max 72 chars, imperative mood, lowercase), and 10 real-world examples covering every type. Fully actionable and copy-paste ready. | 3 / 3 |
Workflow Clarity | The 5 steps are clearly sequenced, but there's no validation checkpoint—e.g., no step to verify the title is under 72 characters or matches the conventional commit regex before submitting. The CI validation section mentions post-hoc checking but doesn't integrate it into the workflow as a pre-submission verification step. | 2 / 3 |
Progressive Disclosure | For a single-purpose skill under 80 lines with no need for external references, the content is well-organized into logical sections (Format, Types, Scope, Steps, Examples, CI Validation) that are easy to scan and navigate. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- MetaMask/metamask-mobile
- Commit
d8db24a
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.