ruby-commit-message
Use when committing code changes in Ruby or Ruby on Rails projects — guides commit message structure, type selection, and body content following Conventional Commits format
76
95%
Does it follow best practices?
Impact
—
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 solid description that clearly communicates when to use the skill and what it does, with good trigger terms scoped to a specific domain. The main weakness is that the specificity of concrete actions could be slightly more detailed — it describes guidance rather than listing discrete capabilities. Overall, it would perform well in a multi-skill selection scenario.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Ruby/Rails commit messages) and mentions some actions (guides commit message structure, type selection, body content), but doesn't list multiple concrete actions like 'generate commit messages, validate format, suggest types'. | 2 / 3 |
Completeness | Explicitly answers both what ('guides commit message structure, type selection, and body content following Conventional Commits format') and when ('Use when committing code changes in Ruby or Ruby on Rails projects') with a clear 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'committing code changes', 'Ruby', 'Ruby on Rails', 'commit message', 'Conventional Commits'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to Ruby/Rails projects and Conventional Commits format. The combination of language-specific (Ruby/Rails) and task-specific (commit message formatting) makes it unlikely to conflict with other skills. | 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 a high-quality skill that is concise, actionable, and well-structured. It provides concrete format templates, multiple realistic examples, and a useful common mistakes table — all without over-explaining concepts Claude already knows. The content is appropriately scoped for its purpose and easy to follow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured. The type table, rules, and examples all earn their place. There's no unnecessary explanation of what commits are or how git works — it assumes Claude's competence and focuses on the specific conventions. | 3 / 3 |
Actionability | Provides a concrete format template, specific rules (imperative mood, 70 char limit, 72 char wrap), complete examples covering multiple scenarios (security fix, new feature, breaking change), and a common mistakes table with fixes. Fully actionable and copy-paste ready. | 3 / 3 |
Workflow Clarity | For a single-task skill (writing commit messages), the workflow is unambiguous: format template → subject rules → body guidelines → footer → examples. The sequence is logical and the common mistakes table serves as a validation checklist. No destructive or batch operations require feedback loops. | 3 / 3 |
Progressive Disclosure | For a self-contained skill under 100 lines with no need for external references, the content is well-organized into clear sections (format, types, subject rules, body guidelines, footer, examples, common mistakes) with appropriate use of tables and headers for easy scanning. | 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.
- Repository
- lucianghinda/superpowers-ruby
- Commit
c037ce3
- 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.