hello-commit

Custom commit workflow that replaces the built-in aif-commit. Demonstrates the skill replacement feature of the extension system.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./examples/extensions/aif-ext-hello/skills/hello-commit/SKILL.md

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-structured for a simple skill, but the commit-message generation step lacks a concrete example and the destructive commit lacks a verification checkpoint. Adding an example commit message and a post-commit verification step would strengthen it.

Suggestions

Provide a concrete example of the generated commit message format (e.g., '[hello] feat: add user login') so the output is unambiguous.

Add a validation step after committing, such as running 'git log -1' to confirm the commit landed correctly.

Specify how to handle the case where 'git diff --cached' shows nothing staged beyond 'suggest staging'.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no padding or explanation of concepts Claude already knows; every line earns its place.	5 / 5
Actionability	Concrete git commands are provided, but 'Generate a commit message with a [hello] prefix' is a high-level hint with no example format, leaving a key detail unspecified.	3 / 5
Workflow Clarity	A clear 5-step sequence with a confirmation checkpoint exists, but the destructive git commit lacks a post-commit verification step, capping workflow clarity at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	This is a short, single-purpose skill under 50 lines with well-organized sections and no need for external references, qualifying for the simple-skill exception.	5 / 5
	Total	16 / 20 Passed

Description

46%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description conveys a clear niche and purpose but lacks an explicit 'when to use' trigger clause and natural user-facing keywords. Adding a 'Use when...' sentence with terms like 'commit message' and 'staged changes' would raise completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when the user wants to commit staged changes').

Include natural trigger phrases such as 'commit message', 'staged changes', or 'git commit' that users would actually say.

List the concrete actions (e.g., 'review staged changes, generate a prefixed commit message, and run git commit') to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('Custom commit workflow') and the concrete action of replacing the built-in aif-commit, plus generating commit messages, but coverage is not comprehensive.	3 / 5
Completeness	There is a clear 'what' (custom commit workflow replacing aif-commit) but no 'Use when...' or equivalent explicit trigger guidance, capping completeness at 3.	3 / 5
Trigger Term Quality	Only the generic keyword 'commit' is present; natural phrases users would say ('commit message', 'staged changes', 'git commit') are missing from the description.	2 / 5
Distinctiveness Conflict Risk	The skill occupies a clear niche (replacing a specific built-in command) with distinct triggers, leaving only minor overlap risk with general commit skills.	4 / 5
	Total	12 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: lee-to/ai-factory
Path: examples/extensions/aif-ext-hello/skills/hello-commit/SKILL.md
Commit: e144f95

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.