Tracks regression tests across releases: maps bug fixes to tests via git commits, tags with pytest/Jest markers, flags coverage gaps, generates reports, enforces via CI.
How this skill is triggered — by the user, by Claude, or both
Slash command
/regression-test-tracker:tracking-regression-testsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
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.
@tag, pytest.mark, JUnit @Tag)fix:, bugfix, closes #, or Jira ticket IDs.regression-tests.json or regression-tests.md) mapping:
// @regression BUG-123 comments or use describe.each with ticket data.@pytest.mark.regression and @pytest.mark.bug("BUG-123") markers.@Tag("regression") and @DisplayName("BUG-123: description").| Error | Cause | Solution |
|---|---|---|
| Regression test passes but bug reappears | Test does not cover the exact failure condition | Review the original bug report; update the test to assert against the specific edge case |
| Orphaned regression tags | Bug ticket was closed as duplicate or invalid | Audit tags quarterly; remove or reassign tests for invalid tickets |
| Regression test consistently skipped | Test marked as skip due to environment issues | Fix the environment dependency or convert to an integration test with proper setup |
| False coverage gap | Bug was fixed by a refactor that removed the vulnerable code path | Mark as "resolved by removal" in the inventory; add a comment explaining why no test is needed |
| Flaky regression test | Non-deterministic timing or data dependency | Stabilize with retries, fixed seeds, or mocked clocks; tag as @flaky for monitoring |
pytest regression test with marker:
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:
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:
{
"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"
}
}
npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skills --plugin regression-test-trackerDerives test regression plans from git history by identifying fix and feature commits lacking tests. Use to find untested bug fixes, coverage gaps, or generate prioritized test backlogs.
Integrates regression testing into CI/CD pipelines using automated baseline comparisons, merge blocking, pre-commit hooks, notifications, and support for GitHub Actions, GitLab CI, and Gitea Actions.
Develop regression test strategies and maintenance approaches. Use when managing regression risk across releases.