Does this skill work with Test-Driven Development (TDD)?

Yes, the skill auto-activates during TDD workflows, guiding you to run quick unit tests during the red-green-refactor cycle and fuller suites upon feature completion.

How does the skill determine which test tier to run?

The skill analyzes the scope of your modifications—such as the number of files changed, whether API/database schemas were touched, and if the logic is user-facing—to recommend the most efficient test tier.

Can I manually override the recommended test tier?

Absolutely. While the skill provides automatic guidance, you can use commands like /test:quick or /test:full to manually trigger the specific level of testing you require.

When should I run E2E tests instead of just Unit tests?

E2E tests should be triggered when user-facing features are modified, authentication flows are updated, or as a final validation step before creating a pull request.

Smart Test Tier Selection

Name: Smart Test Tier Selection
Author: laurigates

bylaurigates

•

Security & Testing

Optimizes development workflows by automatically recommending the appropriate test tier based on the scope and impact of code changes.

About

Smart Test Tier Selection is a specialized Claude Code skill designed to streamline testing strategies by intelligently categorizing changes into Unit, Integration, or E2E tiers. By providing a structured decision matrix and clear escalation signals, it helps developers focus on the most relevant tests for their current task, reducing feedback loops and preventing over-testing. Whether you are performing a minor refactor or launching a multi-file feature, this skill ensures the right level of validation is applied at every stage of the development lifecycle, keeping CI/CD pipelines efficient and code quality high.

Key Features

3 GitHub stars
Automated tier selection based on change scope and file impact
Streamlined command shortcuts for quick feedback and full coverage
Comprehensive decision matrix for UI, API, database, and logic changes
Contextual triggers for consulting specialized test-architecture agents
Defined escalation signals for complex cross-module modifications

Use Cases

Automating the selection of test commands during Test-Driven Development (TDD)
Determining if a local code change requires a quick unit test or a full E2E suite
Standardizing pre-commit testing requirements for team-based development

About

Key Features

3 GitHub stars
Automated tier selection based on change scope and file impact
Streamlined command shortcuts for quick feedback and full coverage
Comprehensive decision matrix for UI, API, database, and logic changes
Contextual triggers for consulting specialized test-architecture agents
Defined escalation signals for complex cross-module modifications

Use Cases

Automating the selection of test commands during Test-Driven Development (TDD)
Determining if a local code change requires a quick unit test or a full E2E suite
Standardizing pre-commit testing requirements for team-based development