CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-commit-push

Use when the user asks to review finished uncommitted work, commit it and push it in one run. Not for planning or implementing, nor when the user stops before the push. Self-contained — execute the inlined steps directly, do NOT invoke other skills.

Quality

73%

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-commit-push/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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 exceptionally well-gated, executable workflow logic — the phase/gate/verification architecture is close to best-in-class — but at roughly double the token cost it needs, and the Push Phase's final steps are corrupted (duplicated, double-numbered, partially nested inside step 6), which undermines both actionability and trust in the generated output. The everything-inlined design ignores progressive disclosure entirely for a very large body.

Suggestions

Deduplicate and compress: the rename-grep rule is stated twice nearly verbatim and 'the report is not the end of the run' is repeated in at least four places — state each once and cross-reference; drop the dated incident notes and war-story rationales, which pad the file without changing runtime behavior.

Repair the Push Phase tail: remove step 7's text from inside step 6's 'Absent' branch parentheses, fix the duplicated '**7. **7. Hand off…' heading to a single '7. **Hand off to the next phase**', and rejoin the 'git worktree add <SCRATCH>/jit-parent-<sid>' command split across lines in Review step 2b.

Move stable methodology detail — the JiT mutant-synthesis/filtering spec, the CI-await tunables and poll-loop contract, and the Reflect audit taxonomy — into reference files the phases read, keeping only the phase skeletons and gates inline to cut the always-loaded footprint substantially.

DimensionReasoningScore

Conciseness

The ~65KB body is noticeably verbose with many padded sections: the renamed-identifier grep rule appears twice nearly verbatim (Commit Phase steps 2 and the mapping list), 'the report is not the end of the run' is restated in the Review report, the Commit→Push gate, the Push→Reflect gate, and Push step 7, and several paragraphs are war-story justification ('This step goes missing in the same way every time…', dated incident notes). Not 1: it is procedural rule text, not explanations of concepts Claude already knows.

2 / 5

Actionability

Guidance is overwhelmingly concrete and executable — exact commands (git rev-parse --abbrev-ref @{u}, git rev-list --left-right --count HEAD...@{u}), exact user prompts, exit-code semantics, and message templates. Not 5 because Push Phase steps 6–7 are structurally corrupted: step 7's full text is embedded in parentheses inside step 6's 'Absent' branch and then duplicated as a malformed double-numbered '**7. **7. Hand off…' step, and a command in Review step 2b ('git worktree add <SCRATCH>/jit-parent-<sid>') is split across a line break, leaving real execution gaps at the push tail.

4 / 5

Workflow Clarity

Sequencing and validation are exemplary: three explicit inter-phase gates, a first-match-wins verdict selection order, STOP semantics defined globally (rule 6) and per gate, a CI poll loop with retry, anomaly cap and investigate handoff, post-push verification, and a closing 15-item verification checklist. This matches anchor 5 (clear sequence, explicit validation, feedback loops, checklists) despite the step-6/7 formatting corruption.

5 / 5

Progressive Disclosure

Internal structure is strong — phase headings, numbered step lists, gates, and a verification section make the monolith navigable — but there is no file split at all: no references/, scripts/, or assets/ exist, and stable methodology detail (JiT mutant synthesis and filtering, CI-await tunables and poll-loop spec, the reflect audit taxonomy) is fully inlined in one ~430-line dense file. Anchor 3 ('content that should be separate is inline') fits; the inlining is partly justified by the no-skill-re-entry rule, which keeps it above anchor 2's 'minimal structure'.

3 / 5

Total

14

/

20

Passed

Description

75%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 strong description with explicit positive and negative trigger guidance and concrete action verbs in the user's natural vocabulary. Its main defect is scope accuracy: the body's Reflect Phase — which edits, commits, and optionally pushes changes to the user's instruction files — is entirely unrepresented, so the description undersells (and under-warns about) a quarter of what the skill does.

Suggestions

Mention the Reflect Phase in the description, e.g. '…push it, then audit the session and apply corrective edits to instruction files, in one run' — the omission hides that the skill edits and commits the user's instruction files.

Add a common synonym such as 'ship' or 'land my changes' to the trigger coverage so users phrasing the request without the word 'push' still match.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("review finished uncommitted work, commit it and push it in one run") plus explicit exclusions, but coverage has a gap: the body's fourth phase (Reflect — auditing the session and editing instruction files) is never mentioned. Anchor 4 ('several specific actions; minor gaps') fits better than 5 (not comprehensive) or 3 (more than 1-2 actions named).

4 / 5

Completeness

Both an explicit 'what' ("review finished uncommitted work, commit it and push it in one run") and an explicit 'when' ("Use when the user asks to…" plus negative triggers "Not for planning or implementing, nor when the user stops before the push") are present. Not 5 because the 'what' materially understates scope: the Reflect Phase — including editing and committing instruction files — is absent, so the description does not fully answer what the skill does.

4 / 5

Trigger Term Quality

Natural trigger phrases users would say are present: "review", "commit", "push", "uncommitted work". A few natural synonyms are missing (e.g. "ship", "send it up", "land it"), which matches anchor 4 rather than 5's comprehensive synonym coverage, and is well above anchor 3's missing common variations.

4 / 5

Distinctiveness Conflict Risk

A clear niche (the tail of the SDLC in a single run) with explicit disambiguation ("Not for planning or implementing… do NOT invoke other skills"). Minor overlap risk remains with closely related sibling composites the body itself references (review-and-commit, ship, ship-task), matching anchor 4 rather than 5's minimal conflict risk.

4 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

Repository

korchasa/flowai-plugins

Path

plugins/flowai/skills/review-commit-push/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.