CtrlK
BlogDocsLog inGet started
Tessl Logo

review-and-commit

Streamlined two-phase workflow: review, then commit. Verdict gate between phases. Self-contained — execute the inlined steps directly, do NOT invoke other skills via the Skill tool.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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

88%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 highly actionable, well-sequenced composite workflow with explicit gates, validation, and feedback loops, presented in a clearly organized section structure; its only real weakness is conciseness given the deliberate full inlining.

DimensionReasoningScore

Conciseness

The body is long but earns its length with actionable procedural detail and assumes Claude's competence (no explanations of git or basic concepts); only minor bookkeeping like the maintainer note could be trimmed.

4 / 5

Actionability

Concrete, copy-paste-ready commands appear throughout ('git diff --stat', 'git worktree add <SCRATCH>/jit-parent-<sid> <parent-sha>', 'deno run -A scripts/check-fr-coverage.ts FR-<ID>') plus a literal report template covering the common cases.

5 / 5

Workflow Clarity

Two phases are explicitly sequenced with validation checkpoints (empty diff guard, pre-flight, verdict gate, verify-unchanged-state, verify-clean-state), feedback loops (re-validate on failure, flaky rerun 3x), and a closing verification checklist.

5 / 5

Progressive Disclosure

Clear section structure (Overview, Context, Rules, Instructions, Verification) with no nested references; the inlining is a deliberate composite design, though at ~370 lines some advanced JiT detail could arguably live in a referenced file.

4 / 5

Total

18

/

20

Passed

Description

61%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, mostly distinct two-phase review-then-commit workflow with natural trigger terms, but it lacks an explicit 'when to use' clause and is light on enumerated concrete actions.

Suggestions

Add a 'Use when ...' clause stating the trigger context (e.g. 'Use when the user wants to review current changes and commit them in one command').

List the concrete actions the skill performs (e.g. runs pre-flight checks, produces a verdict-gated review report, syncs docs, groups and commits with Conventional Commits).

Include common synonyms a user might say ('changes', 'diff', 'PR') alongside 'review' and 'commit'.

DimensionReasoningScore

Specificity

Names the domain and a few concrete actions ('review, then commit', 'Verdict gate between phases'), but coverage is not comprehensive and the remaining text is a constraint rather than a capability.

3 / 5

Completeness

The 'what' is clear (two-phase review-then-commit workflow with a verdict gate), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

'review' and 'commit' are exactly the natural phrases a user would say, but synonyms like 'diff', 'changes', or 'PR' are absent, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The composite review+commit niche with an explicit verdict gate and self-contained framing is mostly distinct, with only minor overlap risk against standalone review or commit skills.

4 / 5

Total

14

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
korchasa/flowai-plugins
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.