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

63%

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

67%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 content is a well-structured, mostly actionable commit workflow with clear sequencing and validation checkpoints. Its main weakness is conciseness, where several rule restatements and the anti-patterns list add length without proportional clarity.

Suggestions

Collapse the anti-patterns bullet list and the consolidation rule into a single compact statement with one example, since the bullets restate the same 'default to one commit' rule three ways.

Tighten the Session Complexity Check (step 6) reflect-invocation prose into a compact conditional rather than a multi-bullet explanation.

Add an explicit validate-then-retry checkpoint for the documentation sync step (e.g., re-read the updated section and confirm it matches the code) to push workflow_clarity toward 5.

Dimension	Reasoning	Score
Conciseness	The body is rule-dense and assumes Claude knows git and Conventional Commits, but the anti-patterns enumeration and verbose rule restatements (e.g., the agent: type and reflect auto-invoke sections) could be tightened, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Concrete commands (`git status -s && ...`, `GIT_PAGER=cat`, `git rm`) and specific file-path scopes appear alongside copy-paste-ready commit-type examples, with only minor abstract gaps in the doc-sync and grouping steps, fitting 'mostly executable guidance; minor gaps'.	4 / 5
Workflow Clarity	An 8-step sequence has explicit checkpoints (clean-tree STOP, verify staged content, final git status) plus an error-handling STOP rule, but some validation is 'report/investigate' rather than a validate-fix-retry loop, so it sits at 'clear sequence with most checkpoints' rather than 5.	4 / 5
Progressive Disclosure	The single self-contained file has clear sections (Overview, Context, Rules, Instructions, Verification) and no nested bundle references, matching 'good structure; most content appropriately placed; minor organization gaps' rather than the reference-signaling 5.	4 / 5
	Total	15 / 20 Passed

Description

58%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 concrete capabilities and a clear niche but omits any explicit 'Use when' trigger guidance, which caps completeness and limits trigger-term coverage. Adding a natural trigger clause would lift the two lowest dimensions.

Suggestions

Append an explicit trigger clause such as 'Use when the user asks to commit, split, or group uncommitted changes, or mentions conventional commits.' to address the missing 'when' and raise completeness above 3.

Add natural user phrasings ('commit my changes', 'split these commits', 'stage and commit') as trigger keywords to improve trigger_term_quality beyond generic terms.

Tighten 'targeted documentation sync — groups the diff into logical commits and updates the docs each change affects' so the doc-sync action reads as a distinct capability rather than a trailing clause, reinforcing distinctiveness.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions (atomic conventional commits, grouping the diff into logical commits, targeted documentation sync), which matches 'lists several specific actions; minor gaps' rather than the comprehensive 5.	4 / 5
Completeness	The 'what' is clear, but there is no 'Use when...' clause or equivalent trigger guidance, so per the rubric completeness is capped at 3 for a clear what with missing when.	3 / 5
Trigger Term Quality	Real keywords like 'commit', 'changes', and 'diff' appear, but common user variations ('split commits', 'write commit messages', 'stage and commit') and an explicit trigger phrase are missing, matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The atomic-commit-plus-doc-sync niche is mostly distinct with only minor overlap risk against adjacent commit skills, fitting 'mostly distinct; minor overlap risk'.	4 / 5
	Total	14 / 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: b4ba256

Reviewed: ~21 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.