commit

Commit current changes as atomic, conventional commits with targeted documentation sync — groups the diff into logical commits and updates the docs each change affects.

Quality

61%

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 ./plugins/flowai/skills/commit/SKILL.md

Quality

Content

56%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 a thorough, actionable commit workflow with clear sequencing and verification, but it is padded with redundant restatements and dated notes, and all detail lives in a single file rather than being split into references.

Suggestions

De-duplicate the 'grep the OLD name' guidance — state it once and reference it from the other locations.

Move dated incident notes ('2026-09-02 and 2026-09-06') out of the body or into a changelog/deprecated section so time-sensitive clutter stops competing for tokens.

Extract the default documentation-map mapping and the commit-type rules into a reference file (e.g. references/doc-sync-map.md) and link to it, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Noticeably verbose: the rename/grep-the-old-name guidance is restated three times, the anti-patterns section repeats rule 1, and dated incident notes ('2026-09-02 and 2026-09-06: ...') add clutter that does not earn its tokens.	2 / 5
Actionability	Provides concrete, executable guidance — a single git-status/diff/log command, GIT_PAGER=cat, explicit DoD-counting logic for task status, and commit-message examples — with only minor gaps.	4 / 5
Workflow Clarity	A clear six-step sequence with substeps, a verification checklist, and an error-handling STOP checkpoint; not a 5 because the error loop halts rather than validating-then-retrying and some checkpoints stay implicit.	4 / 5
Progressive Disclosure	Well sectioned (Overview/Context/Rules/Instructions/Verification) but monolithic: the default doc-map mapping and commit-type rules are substantial content inlined in one file with no external references, and the skill exceeds 50 lines.	3 / 5
	Total	13 / 20 Passed

Description

66%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 is specific and distinct, naming concrete commit and doc-sync actions with relevant trigger terms. Its main weakness is the absence of an explicit 'when to use it' clause, which caps completeness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to commit changes, make a commit, or sync docs to staged work.'

Add common synonyms/extensions such as 'git commit' or 'make commits' to broaden natural trigger coverage.

Optionally mention the conventional-commit type prefixes to hint at the message format the skill enforces.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Commit current changes as atomic, conventional commits', 'groups the diff into logical commits', and 'updates the docs each change affects' — with only minor gaps in coverage.	4 / 5
Completeness	Clearly states what the skill does, but lacks any explicit 'Use when...' trigger guidance; per the judging guideline a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('commit', 'conventional commits', 'documentation sync', 'diff', 'docs') with good coverage, though a few common synonyms like 'git commit' or 'save changes' are absent.	4 / 5
Distinctiveness Conflict Risk	The 'atomic, conventional commits with targeted documentation sync' framing carves a clear niche with minimal conflict risk, though the generic 'commit' trigger could overlap with a plain commit skill.	4 / 5
	Total	15 / 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: korchasa/flowai-plugins
Path: plugins/flowai/skills/commit/SKILL.md
Commit: ad81ae6

Reviewed: 6 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.