tracking-regression-tests

This skill enables Claude to track and run regression tests, ensuring new changes don't break existing functionality. It is triggered when the user asks to "track regression", "run regression tests", or uses the shortcut "reg". The skill helps in maintaining code stability by identifying critical tests, automating their execution, and analyzing the impact of changes. It also provides insights into test history and identifies flaky tests. The skill uses the `regression-test-tracker` plugin.

1.41x

Quality

53%

Does it follow best practices?

Impact

92%

1.41x

Average score across 9 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/testing/regression-test-tracker/skills/regression-test-tracker/SKILL.md

Evaluation results

96%

55%

Setting Up a Regression Test Suite for a Payment Service

Plugin usage and mark flag

Criteria

Without context

With context

Plugin reference

100%

Mark flag syntax

100%

Confirmation language

90%

60%

Critical test selection

100%

Run script uses plugin

100%

Runbook mark workflow

20%

100%

Runbook run workflow

100%

Deployment frequency guidance

100%

Diagnosing Test Instability in a Distributed Inventory Service

Flaky test detection and failure analysis

Criteria

Without context

With context

Failures highlighted

100%

Flaky test identified

100%

Consistent failure identified

100%

Root cause for reorder trigger

100%

Root cause for concurrent update

100%

Root cause for low stock alert

100%

Prioritized action list

80%

100%

75%

Automating Regression Safety Checks for a SaaS Deployment Pipeline

CI/CD integration and deployment frequency

Criteria

Without context

With context

Plugin in CI script

Pre-deployment gate

100%

Deployment blocking

100%

Critical test selection

100%

Mark flag documented

33%

Run frequency guidance

100%

Flaky test mention

100%

Results interpretation

100%

90%

38%

Establishing a Regression Safety Net Before First Production Launch

Pre-launch regression baseline setup

Criteria

Without context

With context

Plugin invoked for marking

100%

Mark flag used

100%

Confirmation per test

Critical path tests selected

100%

Change-risk tests included

100%

Plugin used for run

100%

Pre-deployment frequency

100%

Results include failures

100%

Flaky test awareness

100%

Runbook completeness

100%

97%

36%

Verifying Checkout Logic After a Pricing Engine Refactor

Change-driven regression run and analysis

Criteria

Without context

With context

Change-affected tests identified

100%

Plugin used for marking

100%

Mark flag syntax correct

100%

Plugin used for run

100%

Failures highlighted in report

100%

Root cause per failure

100%

Flaky tests flagged

100%

Confirmation of addition

37%

62%

Prioritized action list

100%

Critical tests not omitted

100%

96%

18%

Cleaning Up a Noisy Regression Suite Before a Major Release

Flaky test triage and suite refinement

Criteria

Without context

With context

Flaky tests identified

100%

Consistent failures identified

100%

Stable tests identified

100%

Root cause per failing test

100%

Flaky root cause or hypothesis

100%

Plugin used for refinement

100%

Mark flag for additions

100%

Critical tests retained

100%

Prioritized recommendations

100%

Confirmation output

100%

50%

100%

22%

Regression Suite Health Review

Test history insights and trend analysis

Criteria

Without context

With context

Flaky tests identified

100%

Consistently failing identified

100%

Stable tests identified

100%

Trend patterns reported

100%

Root cause for flaky tests

100%

Root cause for consistent failure

100%

Plugin used for suite update

100%

Mark flag for additions

100%

Prioritized action recommendations

100%

Suite update confirmation

100%

79%

22%

Hotfix Regression Check Before Emergency Deployment

Emergency hotfix regression verification

Criteria

Without context

With context

Plugin used for marking

50%

Mark flag syntax

80%

Affected tests identified

100%

Plugin used for run

60%

Pre-deployment urgency

100%

Confirmation per test added

100%

Failures highlighted

75%

62%

Root cause per failure

100%

90%

Flaky test handling

37%

Critical path tests selected

100%

40%

Bootstrap Regression Suite for New Inventory Module

Critical test selection for new module regression suite

Criteria

Without context

With context

Plugin used for marking

100%

Mark flag per test

100%

Critical functionality tests selected

100%

Change-likely tests included

100%

Confirmation per test

100%

Selection rationale documented

100%

Low-value tests excluded

100%

Run frequency guidance

25%

100%

Plugin run step documented

100%

Flaky test awareness

100%

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 13d35b8

Evaluated: 2 months ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Setting Up a Regression Test Suite for a Payment Service Diagnosing Test Instability in a Distributed Inventory Service Automating Regression Safety Checks for a SaaS Deployment Pipeline Establishing a Regression Safety Net Before First Production Launch Verifying Checkout Logic After a Pricing Engine Refactor Cleaning Up a Noisy Regression Suite Before a Major Release Regression Suite Health Review Hotfix Regression Check Before Emergency Deployment Bootstrap Regression Suite for New Inventory Module

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.