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
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 solid description that clearly communicates when to use the skill (committing in Ruby/Rails projects) and what it does (guides commit message formatting per Conventional Commits). Its main weakness is that the capability description is somewhat general ('guides structure, type selection, body content') rather than listing discrete concrete actions. The strong trigger terms and explicit 'Use when' clause make it effective for skill selection.
Suggestions
Make capabilities more concrete by listing specific actions, e.g., 'Generates commit messages, suggests conventional commit types (feat, fix, chore), formats message body and footer for Ruby and Ruby on Rails projects.'
| 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 discrete actions — it's more of a general guidance description than specific capabilities like 'generate commit messages, validate format, suggest commit 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). The 'Use when...' clause is present and clear. | 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 help with commit messages in Ruby projects. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to Ruby/Rails projects and Conventional Commits format for commit messages. This clear niche makes it unlikely to conflict with general coding skills, other language-specific skills, or generic git 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 clear format specifications, concrete examples covering multiple scenarios, and a useful common mistakes table. The Ruby/Rails-specific framing (writing for junior developers during debugging) adds genuine value beyond generic Conventional Commits documentation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured. Every section earns its place — the type table is a quick reference, rules are bullet-pointed, and there's no unnecessary explanation of what commits are or how git works. Claude already knows Conventional Commits basics, but the Ruby/Rails-specific framing and the 'write for a junior developer' angle add genuine value. | 3 / 3 |
Actionability | The skill provides a concrete format template, specific rules (imperative mood, 70 char limit, 72 char wrap), three complete real-world examples covering different commit types, and a common mistakes table with fixes. Everything is copy-paste ready and unambiguous. | 3 / 3 |
Workflow Clarity | This is a single-task skill (writing a commit message) with a clear format template and explicit ordering (subject → body → footer). The body guidelines clearly sequence what to include (WHY → WHAT → HOW) with explicit constraints on each. No destructive or batch operations are involved, so no validation checkpoints are needed. | 3 / 3 |
Progressive Disclosure | For a skill of this size and scope, the content is well-organized into logical sections (format, types, subject rules, body guidelines, footer, examples, common mistakes) that progress from structure to details to examples. No external references are needed, and the content doesn't warrant splitting into multiple files. | 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
cb03f92
- 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.