CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/code-change-shape-classifier

Classifies a code change set into four shapes (pure-logic, service-layer, ui-heavy, data-heavy) from file-path and file-content signals, computes the shape distribution over a window of git history, and attaches a relative per-layer test cost model (unit 1x, service 3x, UI 10x) so downstream planning works from one shared input. Produces the classification only: it does not prescribe a target unit:service:UI ratio, does not estimate hours, and does not select which tests to run. Use when a pull request, release branch, or epic needs its change shape labelled before test effort, pyramid balance, or coverage depth is decided.

74

Quality

93%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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 skill body with a clear multi-step workflow and good progressive disclosure via a single verified reference. Its only weakness is moderate verbosity in the conceptual framing and repeated citation prose at the top.

Suggestions

Trim the Overview's explanation of the test-pyramid model and the Mike Cohn provenance — Claude already knows this; keep only the differentiation point.

Consolidate the repeated inline Fowler citation prose (appearances in Overview, Step 3, Step 5, and References) into the single References section to save tokens.

DimensionReasoningScore

Conciseness

Mostly efficient with dense tables and concrete steps, but the Overview explains the test-pyramid concept and credits Mike Cohn's 2009 book, and citation prose is repeated across sections — tightening these would reach the lean level-3 anchor. It is not the verbose concept-padded level-1 anchor.

2 / 3

Actionability

Provides executable commands ('git log --since=... --no-merges --name-only', 'git diff --name-only origin/main...HEAD'), concrete path/content signal tables, a referenced runnable classifier, and a full worked example with real output — copy-paste ready.

3 / 3

Workflow Clarity

A clearly sequenced five-step process (Collect, Classify, Reduce, Compute, Attach cost) with explicit tie-break rules and a 'mixed' flag feeding a human-triage review loop, matching the clear-sequence-with-checkpoints anchor.

3 / 3

Progressive Disclosure

The body is an overview that offloads the runnable classifier detail to a single one-level-deep, well-signaled reference (references/change-shape-classification-script.md, verified present) rather than inlining it, matching the clear-overview-with-one-level-references anchor.

3 / 3

Total

11

/

12

Passed

Description

100%

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 highly specific, third-person description that crisply states what it does, what it deliberately does not do, and when to use it. It is a strong example of a complete, distinctive skill description.

DimensionReasoningScore

Specificity

Names multiple concrete actions in third person — 'Classifies a code change set into four shapes', 'computes the shape distribution', 'attaches a relative per-layer test cost model' — matching the multiple-specific-actions anchor rather than the partial level-2 anchor.

3 / 3

Completeness

Explicitly answers both what and when via the 'Use when a pull request, release branch, or epic needs its change shape labelled...' clause, satisfying the level-3 anchor and not the level-2 'when only implied' anchor.

3 / 3

Trigger Term Quality

Uses natural terms a user would say ('pull request, release branch, or epic', 'test effort, pyramid balance, or coverage depth'), giving good coverage rather than the missing-common-variations level-2 anchor.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (change-shape classification before test decisions) with distinct triggers, unlikely to fire for unrelated skills; above the 'could still overlap' level-2 anchor.

3 / 3

Total

12

/

12

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

Reviewed

Table of Contents