CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

work-unit-commits

Plan commits as reviewable work units. Trigger: commit splitting, chained PRs, or keeping tests and docs with code.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A tight, well-structured instruction skill with concrete rules, examples, commands, and an explicit validation checklist — consistently just short of excellent. The gaps are redundancy across sections, an ODD section that assumes unprovided external context, and no error-recovery guidance when a checklist item fails.

Suggestions

Trim the "When to Use" bullets and the repeated tests/docs-with-code statements to one authoritative location (the Critical Rules table) to tighten conciseness.

Either briefly define or link out for the ODD-specific vocabulary (ask-on-risk, auto-chain, single-pr, exception-ok, ODD feature document) so the ODD Relationship section is actionable on its own.

Add a short feedback loop after the Work Unit Checklist (e.g., "If any box fails, re-slice the change before committing") to complete the workflow's validation cycle.

DimensionReasoningScore

Conciseness

The body is lean — rules tables, a checklist, and short command blocks with no padding or explanation of concepts Claude already knows — but the "When to Use" bullets duplicate the description and the tests/docs-with-code rule is restated across the rules table, checklist, and split examples.

4 / 5

Actionability

Concrete guidance dominates: executable git commands, a weak-vs-better split example table, and a specific pre-commit checklist. However, the ODD section relies on unexplained external vocabulary ("delivery-strategy vocabulary: ask-on-risk, auto-chain, single-pr, exception-ok", "ODD feature document") that is not actionable without outside context.

4 / 5

Workflow Clarity

The PR Relationship section gives a clear numbered sequence and the Work Unit Checklist supplies explicit pre-commit checkpoints, but there is no feedback loop telling Claude what to do when a checklist item fails, leaving a minor validation gap.

4 / 5

Progressive Disclosure

The single file is well organized with clear section headers and needs no external references, but at ~74 body lines it exceeds the simple-skill threshold and mixes general work-unit guidance with ODD-specific process detail that could live in a separate reference.

4 / 5

Total

16

/

20

Passed

Description

78%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 concise, well-structured description that clearly states the skill's purpose and includes an explicit trigger clause with natural terms. Its main weaknesses are limited action coverage (one action) and a few missing common synonyms in the triggers.

Suggestions

List one or two more concrete capabilities alongside planning (e.g., "slice large changes into stacked/chained PRs, and keep tests and docs with the behavior they cover") to raise specificity.

Add common trigger synonyms such as "stacked PRs", "atomic commits", or "split commits" so the description matches more natural user phrasings.

DimensionReasoningScore

Specificity

"Plan commits as reviewable work units" names the domain and one concrete action with a clear manner, matching the 1-2-concrete-actions anchor; it does not list several specific actions needed for a 4.

3 / 5

Completeness

It clearly answers both what ("Plan commits as reviewable work units") and when (an explicit "Trigger:" clause listing three concrete trigger phrases), matching the both-what-and-when anchor with concrete triggers.

5 / 5

Trigger Term Quality

"Trigger: commit splitting, chained PRs, or keeping tests and docs with code" provides good natural keyword coverage, but misses common synonyms and variations a user might say such as "stacked PRs", "atomic commits", or "split commits".

4 / 5

Distinctiveness Conflict Risk

The commit-splitting/chained-PR niche is mostly distinct with specific triggers, but the commit-related triggers (especially "keeping tests and docs with code") carry minor overlap risk with closely related commit-message or git-hygiene skills.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Gentleman-Programming/gentle-ai

Path

internal/assets/skills/work-unit-commits/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.