CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/regression-suite-selector

Builds a CI workflow that runs only the subset of tests impacted by a PR's changes - combines a per-test → source-file dependency map (built from coverage profiles or, in build-graph projects, queried from the build system itself like Bazel `rdeps`) with the PR's `git diff --name-only`, then selects the union of (impacted by changed files + previously failing + newly added). Always pairs with a periodic full-suite run so a misconfigured map can't silently shrink coverage. Use when the regression suite is large enough that PR-time CI is the bottleneck and a full run is reserved for nightly / pre-release.

79

Quality

99%

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

Overview
Quality
Evals
Security
Files

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-engineered, token-efficient skill: executable core logic inline, supporting detail in a real one-level reference, an explicit safety/validation feedback loop, and a dense anti-patterns checklist. It exemplifies the score-3 anchors across all four content dimensions.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — executable code, compact tables, and a tight anti-patterns table with no basics-fluff (the TIA framing is specialized knowledge, not a 'what is a PDF' explanation), and no time-sensitive pins that would age. Not score 2 because nothing reads as unnecessary padding that could simply be cut without loss.

3 / 3

Actionability

Provides executable Python (build_map, select_tests), a concrete git diff command, and a copy-paste PR-comment template, with per-framework recipes and CI YAML in a real reference file; not score 2 because the inline code is complete and executable rather than pseudocode.

3 / 3

Workflow Clarity

Seven clearly sequenced steps with explicit validation in Step 5 (run selected T1 then all T2 and confirm they agree), an explicit feedback loop (shadow full run → investigate drift → update map), fallback-to-full-suite error recovery, and an anti-patterns checklist; batch-operation validation is present so workflow clarity is not capped at 2.

3 / 3

Progressive Disclosure

Core selector logic stays inline while per-framework instrumentation and the CI workflow are offloaded to references/instrumentation-and-ci.md, signaled twice (Step 2, Step 5) and one level deep (verified: the reference does not nest further); not score 2 because content is appropriately split with clear navigation.

3 / 3

Total

12

/

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 dense, specific description that states concrete actions, an explicit third-person 'Use when' trigger, and a distinct niche. Its only weakness is verbosity — heavy mechanism detail (rdeps, per-test dependency map) that arguably belongs in the body rather than the description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Builds a CI workflow that runs only the subset of tests impacted by a PR's changes', 'combines a per-test → source-file dependency map ... with the PR's git diff --name-only, then selects the union of (impacted by changed files + previously failing + newly added)' — matching the score-3 anchor of multiple specific concrete actions rather than the partial listing of score 2.

3 / 3

Completeness

Clearly answers both what ('Builds a CI workflow that runs only the subset of tests impacted...') and when (explicit 'Use when...' clause), so it is not capped at 2 per the missing-trigger guideline; uses third-person voice so no specificity penalty.

3 / 3

Trigger Term Quality

The explicit 'Use when the regression suite is large enough that PR-time CI is the bottleneck and a full run is reserved for nightly / pre-release' gives good coverage of natural terms (CI, regression suite, PR, full-suite run, bottleneck) a user would actually say; not score 2 because natural trigger terms are well covered, not just 'some relevant keywords'.

3 / 3

Distinctiveness Conflict Risk

Test Impact Analysis for PR-time CI is a clear, narrow niche with distinct triggers unlikely to overlap with sibling skills like coverage-debt-tracker; not score 2 because it is not merely 'somewhat specific'.

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: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents