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.
96
95%
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 narrow purpose and includes an explicit 'Use when' clause with natural trigger terms. Its main weakness is that it describes only a single action rather than listing multiple specific capabilities, but given the focused nature of the skill, this is a minor issue. Overall it would perform well in skill selection among a large set of skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (PR titles, git diffs) and one core action (generate a conventional commit PR title from git diff analysis), but doesn't list multiple concrete actions beyond that single capability. | 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 like generating PR titles, writing pull request titles, or creating conventional commit titles). | 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 — conventional commit PR titles from git diffs. Unlikely to conflict with general commit message skills or other code review skills due to the explicit focus on PR titles and conventional commit format. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent, well-crafted skill. It's concise yet comprehensive, with a clear format specification, actionable steps with real git commands, a thorough type reference table, and abundant concrete examples. The content respects Claude's intelligence while providing all the project-specific context needed (scope conventions, CI validation details).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section earns its place — the type table is a quick reference, scopes are listed without over-explanation, and there's no unnecessary preamble about what conventional commits are or why they matter. | 3 / 3 |
Actionability | Provides concrete git commands, a clear format specification, a comprehensive type table, and 10 fully-formed examples covering every type. Claude can directly produce correct output from this guidance. | 3 / 3 |
Workflow Clarity | The 5-step process is clearly sequenced with specific commands. This is a non-destructive, single-output task (generating a title string), so validation/feedback loops are not critical. The CI validation section serves as an implicit verification checkpoint. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with a single focused task, the content is well-organized into logical sections (Format, Types, Scope, Steps, Examples, CI Validation) with no need for external references. Navigation is clear via headers. | 3 / 3 |
Total | 12 / 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.
bee9b14
Table of Contents
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.