Menu
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".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Implement user sign-up and sign-in flows with Clerk. Use when building authentication UI, customizing sign-in experience, or implementing OAuth social login. Trigger with phrases like "clerk sign-in", "clerk sign-up", "clerk login flow", "clerk OAuth", "clerk social login".
Implement session management and middleware with Clerk. Use when managing user sessions, configuring route protection, or implementing token refresh and custom JWT templates. Trigger with phrases like "clerk session", "clerk middleware", "clerk route protection", "clerk token", "clerk JWT".
Configure enterprise SSO, role-based access control, and organization management. Use when implementing SSO integration, configuring role-based permissions, or setting up organization-level controls. Trigger with phrases like "clerk SSO", "clerk RBAC", "clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".
Create your first authenticated request with Clerk. Use when making initial API calls, testing authentication, or verifying Clerk integration works correctly. Trigger with phrases like "clerk hello world", "first clerk request", "test clerk auth", "verify clerk setup".
Install and configure Clerk SDK/CLI authentication. Use when setting up a new Clerk integration, configuring API keys, or initializing Clerk in your project. Trigger with phrases like "install clerk", "setup clerk", "clerk auth", "configure clerk API key", "add clerk to project".
Use when two or more agent sessions — same or different platforms (Claude Code, Codex, Gemini CLI, Copilot, Cursor) — work the same repo concurrently, hand off in-flight work, or need to interrogate each other about a handoff. Triggers: "set up comms with the other session", "hand this off to Codex/Gemini", "grill the handoff", "check the mailbox", parallel sessions clobbering shared files, resuming work another agent left half-done. Trigger with "/walkie-talkie".
| 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-*) |
| version | 1.26.0 |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| license | MIT |
| tags | ["testing","tracking-regression"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
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"
}
}