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

83%

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 well-structured, actionable instruction skill: concrete rules, a numeric size guard, real commit-message examples, and a validation checklist. The main improvements are consolidating the duplicated verification requirements between the checklist and the ODD section and defining the delivery-strategy vocabulary it references.

DimensionReasoningScore

Conciseness

The body is efficient — rule tables, checklists, and terse sections with no explanation of concepts Claude already knows. It is not 5 because the verification requirements ('Focused test command and exact result', 'Runtime harness command/scenario...', 'Rollback boundary...') are repeated nearly verbatim in both the Work Unit Checklist and the ODD 'implementation evidence' list and could be consolidated.

4 / 5

Actionability

Concrete guidance throughout: exact commands ('git diff --stat', 'git log --oneline -5'), a numeric threshold ('>400 changed lines'), and real commit-message examples ('feat(auth): add token validation domain model and tests'). Not 5 because the delivery-strategy vocabulary ('ask-on-risk', 'auto-chain', 'single-pr', 'exception-ok') is named but never defined, and no example of a runtime harness command/scenario is given.

4 / 5

Workflow Clarity

The 'PR Relationship' section gives a numbered sequence (build unit, verify, commit, promote to chained PRs at the 400-line threshold) and the Work Unit Checklist is an explicit pre-commit validation checkpoint. Not 5 because there is no feedback loop for what to do when a checklist item fails — re-splitting is only implied.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed; the content is overview-level with clear sections (When to Use, Critical Rules, Checklist, Examples, PR/ODD Relationships, Commands). Not 5 because the body is ~89 lines — above the under-50-line simple-skill exception — and the dense ODD section duplicates checklist content rather than being consolidated.

4 / 5

Total

16

/

20

Passed

Description

83%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: it states a clear capability, uses third person, and pairs it with an explicit, concrete trigger clause. Trigger coverage is good but could add common synonyms like 'stacked PRs' or 'atomic commits' for comprehensiveness.

DimensionReasoningScore

Specificity

Names several concrete capabilities — 'Plan commits as reviewable work units', 'commit splitting, chained PRs, or keeping tests and docs with code' — matching the anchor for several specific actions with minor gaps. It falls short of 5 because 'reviewable work units' is somewhat abstract and coverage is not comprehensive (e.g., no commit-message or stack-management wording).

4 / 5

Completeness

'Plan commits as reviewable work units' explicitly answers what the skill does, and 'Trigger: commit splitting, chained PRs, or keeping tests and docs with code' explicitly answers when with concrete trigger phrases — the top anchor. The 'when' clause is explicit and specific, so the 4 anchor ('could be more explicit') does not fit.

5 / 5

Trigger Term Quality

'commit splitting', 'chained PRs', and 'keeping tests and docs with code' are natural phrases a user would say when needing this skill, matching the good-coverage anchor. It is not 5 because common synonyms such as 'stacked PRs' or 'atomic commits' are missing.

4 / 5

Distinctiveness Conflict Risk

The commit-splitting and chained-PR niche is mostly distinct from adjacent skills (e.g., commit-message generation) with dedicated triggers. Minor overlap risk remains with general PR-preparation or git-workflow skills via 'keeping tests and docs with code', so it is not 5.

4 / 5

Total

17

/

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

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.