ac-commit-manager

Manage git commits for autonomous coding. Use when committing feature implementations, creating descriptive commits, managing git workflow, or handling version control.

Quality

78%

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 ./skills/ac-commit-manager/SKILL.md

Quality

Content

75%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.

A strong, code-forward skill body: every code example matches the bundled implementation exactly and is executable as written, and the commit workflow is clearly sequenced with validation built in. The main costs are modest padding (a redundant Purpose section, an explanation of conventional-commit types Claude already knows) and the absence of error-recovery guidance for when pre-commit validation or verification fails.

Suggestions

Delete the 'Purpose' section (it restates the opening line) and the conventional-commit category list (feat/fix/docs/chore is knowledge Claude already has), keeping only any non-standard categories actually enforced by the script.

Add a feedback loop to the commit workflow: what to do when pre_commit_check() returns can_commit=false or when the VERIFY step fails (e.g., fix tests/lint, re-run validation, or roll back the partial commit).

Move the full commit-result JSON example into a reference file (or trim it to the fields a caller actually reads) and expand the bare 'API Reference' pointer with the module-level convenience function and config options.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (tight sections, terse lists, code-forward), but it includes unnecessary explanation: the 'Purpose' section restates the opening line, the commit-categories list explains conventional-commit types (feat/fix/docs/chore) Claude already knows, and 'Atomic Commits' states obvious properties ('self-contained and revertable'). This is more than the 'minor instances' of anchor 4, fitting anchor 3.	3 / 5
Actionability	All code examples are executable and verified against the bundled scripts/commit_manager.py: CommitManager(project_dir), await manager.commit_feature(...), pre_commit_check(), rollback_last_commit(), and rollback_to_feature(...) all exist with exactly these signatures. The message-format, configuration, and commit-result examples are concrete and copy-paste ready, covering the common cases.	5 / 5
Workflow Clarity	The six-step workflow (VALIDATE → STAGE → MESSAGE → COMMIT → VERIFY → TAG) is clearly sequenced with a validation checkpoint up front and verification after, plus an enumerated pre-commit checklist and working pre_commit_check() code. It falls short of anchor 5 because there are no error-recovery feedback loops — nothing says what to do when validation or verification fails, and the rollback section is not wired into the main flow.	4 / 5
Progressive Disclosure	Sections are well organized and implementation detail is correctly deferred via a single, clearly signaled one-level reference ('See scripts/commit_manager.py for full implementation') to a file that exists in the bundle. It stays at anchor 4 rather than 5 because the 'API Reference' section is a bare pointer with no navigable detail, and inline content like the full 17-line commit-result JSON could be split into reference material.	4 / 5
	Total	16 / 20 Passed

Description

70%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.

A solid description with an explicit and well-structured 'Use when...' trigger clause and mostly natural keywords. Its main weakness is that the 'what' is thin — the action verbs are largely synonymous variations on 'commit' rather than a concrete inventory of capabilities (message generation, pre-commit validation, tagging, rollback).

Suggestions

List the distinct concrete capabilities in the 'what' portion, e.g., 'Generate structured commit messages, run pre-commit validation, tag milestone commits, and roll back feature commits' instead of the generic 'Manage git commits for autonomous coding'.

Add the natural trigger phrase 'commit message(s)' and 'git commit' to the 'Use when' clause, since users asking for commit-message help would benefit from matching this skill.

Trim the redundant generic triggers ('managing git workflow', 'handling version control') which add no specificity and increase overlap risk with general git skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Manage git commits') and one concrete action ('creating descriptive commits'), but the remaining phrases ('committing feature implementations', 'managing git workflow', 'handling version control') are generic variations of the same act rather than distinct concrete capabilities. It fits anchor 3 (domain plus 1-2 concrete actions, not comprehensive); anchor 4 requires several genuinely specific actions.	3 / 5
Completeness	Both parts are present: 'Manage git commits for autonomous coding' states what it does, and an explicit 'Use when committing feature implementations, creating descriptive commits, managing git workflow, or handling version control' clause states when. It falls short of anchor 5 because the 'what' is minimal — it does not convey message generation, pre-commit validation, tagging, or rollback.	4 / 5
Trigger Term Quality	Terms like 'committing', 'commits', 'git workflow', and 'version control' are natural phrases a user would say when needing this skill. A few common variations are missing (e.g., 'commit message', 'git commit', 'make a commit'), matching anchor 4's 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym-and-extension coverage of anchor 5.	4 / 5
Distinctiveness Conflict Risk	The 'for autonomous coding' scoping and feature-implementation triggers carve out a fairly distinct niche with minimal conflict risk. There is minor overlap risk with generic commit-message-generation or git-hygiene skills, matching anchor 4 rather than the fully distinct niche of anchor 5.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: fernandezbaptiste/Skrillz
Path: skills/ac-commit-manager/SKILL.md
Commit: 93ed392

Reviewed: 13 hours 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.