Agent skill

Tracking Regression Tests

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Track and manage regression test suites across releases. An agent skill from jeremylongshore/tons-of-skills-marketplace.

MITAuto-check passedTesting & QA

Install Tracking Regression Tests

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill tracking-regression-tests -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace tracking-regression-tests --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/tracking-regression-tests .claude/skills/tracking-regression-tests && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tracking-regression-tests
GitHub stars
2.8k
Token cost
~1.4k tokens
SKILL.md length
513 words
Files
10 (incl. scripts, references, assets)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Track and manage regression test suites across releases. An agent skill from jeremylongshore/tons-of-skills-marketplace.

  • Works in 7 steps: Scan the codebase with Grep for bug-fix… → For each bug-fix commit, check whether a… → Create a regression test inventory file… → …
  • Performing specialized testing
  • SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 3 more sections
  • Runs Python scripts from its folder

What it does

Tracking Regression Tests is an agent skill from jeremylongshore/tons-of-skills-marketplace. Track and manage regression test suites across releases. Use when performing specialized testing. Trigger with phrases like "track regressions", "manage regression suite", or "validate against baseline".

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts, reference files and assets (for example `assets/README.md`, `assets/config_template.yaml` and `assets/example_test_history.json`). Compatibility notes: Designed for Claude Code

It sits in Testing & QA, covering Unit testing. It works with pytest and JUnit. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Performing specialized testing
  • With phrases like track regressions
  • Manage regression suite
  • Validate against baseline

Example prompts

  • “track regressions”
  • “manage regression suite”
  • “validate against baseline”
  • “/tracking-regression-tests”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Grep, Glob, Bash(test:regression-*)

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Scan the codebase with Grep for bug-fix commits by searching commit messages for patterns like fix:, bugfix, closes #, or Jira ticket IDs.
  2. For each bug-fix commit, check whether a corresponding regression test exists
  3. Create a regression test inventory file (regression-tests.json or regression-tests.md) mapping
  4. Tag existing regression tests with metadata for traceability
  5. Generate a regression coverage report showing
  6. Set up a CI check that fails the build if a bug-fix PR does not include at least one regression test.
  7. Schedule periodic audits (weekly or per-release) to verify all regression tests still pass and remain relevant.

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Grep
    • Glob
    • Bash(test:regression-*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 4 files in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.pytest.org
    • junit.org
    • jestjs.io
    • martinfowler.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Tracking Regression Tests loads about 1.4k tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 57 tokens; SKILL.md has 513 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 513 words, ~1,353 tokens.

Download SKILL.mdSave it as .claude/skills/tracking-regression-tests/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
tracking-regression-tests
description
Track and manage regression test suites across releases. Use when performing specialized testing. Trigger with phrases like "track regressions", "manage regression suite", or "validate against baseline".
allowed-tools
Read, Write, Edit, Grep, Glob, Bash(test:regression-*)
compatibility
Designed for Claude Code
version
1.26.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
testing, tracking-regression

Regression Test Tracker

Overview

Track, manage, and maintain regression test suites across releases to ensure previously fixed bugs stay fixed and existing features remain stable. Maps regression tests to bug tickets, monitors test health over time, and identifies gaps where fixed bugs lack corresponding regression tests.

Prerequisites

  • Test framework with tagging or marking support (@tag, pytest.mark, JUnit @Tag)
  • Bug tracking system with issue IDs (GitHub Issues, Jira, Linear)
  • Git history accessible for correlating bug fixes with test additions
  • Existing test suite with named test cases
  • CI pipeline producing test result artifacts (JUnit XML or JSON)

Instructions

  1. Scan the codebase with Grep for bug-fix commits by searching commit messages for patterns like fix:, bugfix, closes #, or Jira ticket IDs.
  2. For each bug-fix commit, check whether a corresponding regression test exists:
    • Search test files for the bug ticket ID in test names, comments, or tags.
    • Verify the test exercises the specific code path that was fixed.
    • Flag fixes without regression tests as coverage gaps.
  3. Create a regression test inventory file (regression-tests.json or regression-tests.md) mapping:
    • Bug ticket ID to test file and test name.
    • Severity of the original bug (critical, high, medium, low).
    • Date the regression test was added.
    • Current test status (passing, failing, skipped).
  4. Tag existing regression tests with metadata for traceability:
    • Jest: Add // @regression BUG-123 comments or use describe.each with ticket data.
    • pytest: Apply @pytest.mark.regression and @pytest.mark.bug("BUG-123") markers.
    • JUnit: Use @Tag("regression") and @DisplayName("BUG-123: description").
  5. Generate a regression coverage report showing:
    • Total bugs fixed vs. bugs with regression tests (coverage percentage).
    • Untested regressions ranked by severity.
    • Tests that have become flaky or were disabled.
  6. Set up a CI check that fails the build if a bug-fix PR does not include at least one regression test.
  7. Schedule periodic audits (weekly or per-release) to verify all regression tests still pass and remain relevant.
Show full SKILL.md (207 more words)Show less

Output

  • Regression test inventory file mapping bugs to tests
  • Tagged test files with regression markers and ticket references
  • Coverage gap report listing bug fixes without regression tests
  • CI configuration for regression test enforcement
  • Release readiness checklist based on regression suite pass rate

Error Handling

ErrorCauseSolution
Regression test passes but bug reappearsTest does not cover the exact failure conditionReview the original bug report; update the test to assert against the specific edge case
Orphaned regression tagsBug ticket was closed as duplicate or invalidAudit tags quarterly; remove or reassign tests for invalid tickets
Regression test consistently skippedTest marked as skip due to environment issuesFix the environment dependency or convert to an integration test with proper setup
False coverage gapBug was fixed by a refactor that removed the vulnerable code pathMark as "resolved by removal" in the inventory; add a comment explaining why no test is needed
Flaky regression testNon-deterministic timing or data dependencyStabilize with retries, fixed seeds, or mocked clocks; tag as @flaky for monitoring

Examples

pytest regression test with marker:

python
import pytest

@pytest.mark.regression
@pytest.mark.bug("GH-1042")  # 1042 = configured value
def test_csv_export_handles_unicode_characters():
    """Regression: GH-1042 -- CSV export crashed on non-ASCII names."""
    result = export_csv([{"name": "Rene"}])
    assert "Rene" in result
    assert result.startswith("name\n")

Jest regression test with ticket reference:

typescript
describe('BUG-789: Cart total calculation', () => {  # 789 = configured value
  it('applies percentage discount before tax', () => {
    const cart = createCart([{ price: 100, qty: 2 }]);
    cart.applyDiscount({ type: 'percent', value: 10 });
    expect(cart.subtotal).toBe(180);
    expect(cart.tax).toBe(18); // 10% tax on discounted subtotal
  });
});

Regression inventory entry:

json
{
  "BUG-1042": {  # 1042 = configured value
    "test_file": "tests/test_export.py::test_csv_export_handles_unicode_characters",
    "severity": "high",
    "added": "2026-01-15",  # 2026 year
    "status": "passing"
  }
}

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (scripts, references, assets) in skills/.curated/tracking-regression-tests of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • assets/README.md
  • assets/config_template.yaml
  • assets/example_test_history.json
  • assets/test_report_template.md
  • references/README.md
  • scripts/README.md
  • scripts/analyze_test_history.py
  • scripts/mark_test_as_regression.py
  • scripts/run_regression_tests.py

Open the folder on GitHubat commit cfae287

Compare with similar skills

Tracking Regression Tests next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tracking Regression Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tracking Regression Tests this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.4kAutomated safety check: PassMIT
Blue Teamgaasher/Agent-Loop-Skills174—~3.6kAutomated safety check: PassMIT
Test Analysis Extensionsmicrosoft/testfx1k2 repos~1.1kAutomated safety check: PassMIT
TDD Guidealirezarezvani/claude-skills28k—~3.4kAutomated safety check: PassMIT
TDD GuideLeoYeAI/openclaw-master-skills2.2k—~1.4kAutomated safety check: PassMIT
TDD Guideborghei/Claude-Skills891—~1.7kAutomated safety check: PassMIT

Similar skills

  • Blue Team

    gaasher/Agent-Loop-Skills

    A skill your agent uses when the user has concrete failing cases in code or a guardrail/classifier/filter/prompt/API they own — a red-team failure catalogue OR a CI/CD test-failure report (failing…

    174 GitHub stars~3.6k tokensUpdated 3 mo ago
    Testing & QAAuto-check passed
  • Test Analysis Extensions

    microsoft/testfx

    Official

    Provides file paths to language-specific reference files for the test ANALYSIS skills (assertion-quality, test-anti-patterns, test-gap-analysis, test-smell-detection, test-tagging).

    1k GitHub starsUsed in 2 repos~1.1k tokens
    Testing & QAAuto-check passed
  • TDD Guide

    alirezarezvani/claude-skills

    Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and…

    28k GitHub stars~3.4k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • TDD Guide

    LeoYeAI/openclaw-master-skills

    Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and…

    2.2k GitHub stars~1.4k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed
  • TDD Guide

    borghei/Claude-Skills

    Guide red-green-refactor TDD with test generation, coverage-gap analysis, and multi- framework support.

    891 GitHub stars~1.7k tokensUpdated 3 days ago
    Testing & QAAuto-check passed
  • TDD Guide

    aAAaqwq/AGI-Super-Team

    Test-driven development workflow with test generation, coverage analysis, and multi-framework support

    105 GitHub starsUsed in 2 repos~1.1k tokens
    Testing & QAAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Tracking Regression Tests

What does Tracking Regression Tests do?

Track and manage regression test suites across releases. An agent skill from jeremylongshore/tons-of-skills-marketplace. Tracking Regression Tests is an agent skill from jeremylongshore/tons-of-skills-marketplace. Track and manage regression test suites across releases.

When should I use Tracking Regression Tests?

Tracking Regression Tests fits situations like: performing specialized testing; with phrases like track regressions; manage regression suite; validate against baseline.

How do I install Tracking Regression Tests in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill tracking-regression-tests -a claude-code`. Or copy the skill folder (skills/.curated/tracking-regression-tests in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/tracking-regression-tests in your project. Claude Code loads it when a task matches its description.

How do I install Tracking Regression Tests in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill tracking-regression-tests -a codex`. Or copy the skill folder (skills/.curated/tracking-regression-tests in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/tracking-regression-tests in your project. Codex loads it when a task matches its description.

Can I use Tracking Regression Tests in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill tracking-regression-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tracking-regression-tests, .gemini/skills/tracking-regression-tests, .github/skills/tracking-regression-tests and .opencode/skills/tracking-regression-tests in your project.

What does Tracking Regression Tests need to run?

Going by SKILL.md and its folder, Tracking Regression Tests needs Python for the scripts in its folder. Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Edit, Grep, Glob, Bash(test:regression-*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Tracking Regression Tests access the network?

SKILL.md names 4 domains. As links in the text: docs.pytest.org, junit.org, jestjs.io and martinfowler.com. This is read from the text; nothing was executed.

Is Tracking Regression Tests safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Tracking Regression Tests use?

Tracking Regression Tests is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tracking Regression Tests use?

About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 17 tokens, read only when the agent opens those files.

What are the alternatives to Tracking Regression Tests?

Skills that share tags, products or a category with Tracking Regression Tests: Blue Team (gaasher/Agent-Loop-Skills, 174 stars), Test Analysis Extensions (microsoft/testfx, 1k stars), TDD Guide (alirezarezvani/claude-skills, 28k stars) and TDD Guide (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tracking Regression Tests?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.