CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-and-commit

Use when the user asks to review the uncommitted changes and then commit them — the verdict gates the commit. Not for a review alone or a plain commit. Self-contained — execute the inlined steps directly, do NOT invoke other skills.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/flowai/skills/review-and-commit/SKILL.md
SKILL.md
Quality
Evals
Security

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 delivers an exceptionally well-gated, checkpoint-rich workflow with concrete commands and decision rules, but at roughly twice the token budget the task needs: rules are duplicated, prose walls justify each instruction at length, and cross-references to undefined rules (10–13, 6) leave parts of the gating logic unresolvable. It reads as three full skills concatenated rather than one streamlined composite, as its own overview claims.

Suggestions

State each rule once: the grep-the-old-name guidance appears nearly verbatim twice in Phase 2 step 2, and the parent-worktree/never-stash prohibitions are restated across steps 2b and 8b — keep the first statement and reference it elsewhere.

Resolve the dangling rule references: "Rule 10", "Rule 11", "Rule 12", "Rule 13", and "Rule 6" are cited but the <rules> section defines only 1–6 — either include the full rule list or inline the operative text at each citation site.

Split the JiT sub-workflow (steps 2b, 3d/3e, 8a/8b and the parent-worktree lifecycle) into a single referenced file with a short trigger condition in the main body — it is a self-contained subset whose bulk drives most of the file's token cost.

DimensionReasoningScore

Conciseness

The body is pervasively padded: step 2b and the Parallel Delegation bullet are multi-hundred-word prose walls, rhetorical asides abound ("A question followed in the same breath by 'pushing now' is not a question, it is an announcement"), and rules are restated nearly verbatim — the grep-the-old-name rule appears twice in Phase 2 step 2, and the parent-worktree prohibitions recur across steps 2b and 8b. Not 3: the verbosity is constant rather than occasional; not 1: it never explains concepts Claude already knows and most text is operative instruction.

2 / 5

Actionability

Guidance is largely executable — exact commands ("git worktree add <SCRATCH>/jit-parent-<sid> <parent-sha>", "git diff --stat"), an explicit first-match verdict-selection order, a concrete report template, and push-safety checks. Not 5: the text cites "Rule 10", "Rule 11", "Rule 12", "Rule 13", and "Rule 6" but the <rules> section defines only rules 1–6, leaving those citations dangling; not 3: the bulk of the guidance is directly executable, not high-level hints.

4 / 5

Workflow Clarity

Three phases are strictly sequenced behind an explicit verdict gate ("Only Approve proceeds to Phase 2"), with validation checkpoints throughout (empty-diff guard, "Verify Unchanged State", the dual-run filter ensemble, the two pre-reset checks before `git reset --hard`) and a closing verification checklist. Not 5: the undefined Rule 13 reference sits inside the verdict-selection logic itself, so part of the gating cannot be followed from this file alone; well above 3: checkpoints and error-recovery fallbacks are explicit and pervasive.

4 / 5

Progressive Disclosure

No bundle files exist — all three inlined workflows live in one ~350-line monolithic file, which is a deliberate, justified design ("Self-contained — execute the inlined steps directly, do NOT invoke other skills") but still leaves phase-scale content inlined that could be split. Internal structure is strong (phases, <step_by_step> blocks, rules, verification), so above anchor 2's "minimal structure"; below anchor 4 because nothing is organized into separate files.

3 / 5

Total

13

/

20

Passed

Description

82%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 an exemplar of trigger hygiene: an explicit "Use when" clause, concrete what/when answers, and explicit negative boundaries that separate it from plain review or plain commit skills. Its only weakness is specificity — it names the two top-level actions but not what the review phase actually covers.

DimensionReasoningScore

Specificity

"review the uncommitted changes and then commit them" names the domain plus two concrete actions and the gating mechanism ("the verdict gates the commit"), but does not enumerate what the review covers (QA, doc sync, reflection), so coverage is not comprehensive. Not 4: only two top-level actions are listed with no breakdown; not 2: the actions named are concrete, not generic.

3 / 5

Completeness

Explicitly answers both questions: the "what" is "review the uncommitted changes and then commit them — the verdict gates the commit", and the "when" is an explicit "Use when the user asks to review the uncommitted changes and then commit them", reinforced with negative boundaries ("Not for a review alone or a plain commit"). Not 4: the when-clause is fully explicit with concrete trigger conditions and exclusions, not merely present or implicit.

5 / 5

Trigger Term Quality

"review", "uncommitted changes", and "commit" are natural phrases users would actually say when they need this skill. Not 5: common synonyms and variations ("staged changes", "pending changes", "commit my changes") are missing; not 3: the core trigger phrasing matches how the request is naturally expressed.

4 / 5

Distinctiveness Conflict Risk

The composite occupies a clear niche (review-then-commit with a verdict gate) and actively disambiguates from its nearest conflicting skills: "Not for a review alone or a plain commit." Not 4: overlap risk with sibling review/commit skills is explicitly excluded rather than merely minor.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

korchasa/flowai-plugins

Path

plugins/flowai/skills/review-and-commit/SKILL.md

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.