Regression Testing

When the user wants to prevent regressions, improve test coverage, or says 'add tests,' 'improve coverage,' 'we keep breaking this,' 'write regression tests,' 'characterization tests,' or after fixing a production bug to ensure it never recurs.

43 starsTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add 0xranx/agentbrief --skill regression-testing
Manual install
git clone --depth 1 https://github.com/0xranx/agentbrief.git /tmp/agentbrief
mkdir -p ~/.claude/skills
cp -r /tmp/agentbrief/briefs/qa-engineer/skills/regression-testing ~/.claude/skills/regression-testing

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Regression Testing

You are writing tests specifically to prevent regressions — bugs that were fixed but could come back.

## Process

### 1. Identify Regression Risks

High-risk areas for regressions:
- Code that was recently fixed (the fix might be incomplete)
- Code that's frequently modified (high churn = high risk)
- Code with complex conditional logic (many branches = many ways to break)
- Code at integration boundaries (where two systems meet)
- Code without any existing tests

### 2. Write Characterization Tests

Before changing any code, capture current behavior:

```typescript
// Characterization test: documents current behavior
// If this test breaks during refactoring, you changed behavior (intentionally or not)
it('should return empty array when no items match filter', () => {
  const result = filterItems([], { status: 'active' });
  expect(result).toEqual([]);
});
```

### 3. Write Regression Tests for Fixed Bugs

Every bug fix needs a regression test:

```typescript
// Regression: https://github.com/org/repo/issues/123
// Bug: Processing failed when input contained unicode emoji
it('should handle unicode emoji in input', () => {
  const result = processInput('Hello 👋 World');
  expect(result.text).toBe('Hello 👋 World');
});
```

Rules for regression tests:
- Reference the original issue/bug in a comment
- Test the exact scenario that triggered the bug
- Test close variants (if emoji broke it, test other unicode too)
Read the full skill on GitHub

Details

Skill name
regression-testing
Path
briefs/qa-engineer/skills/regression-testing/SKILL.md
License
MIT
Repo updated
28 March 2026

FAQ

What does the Regression Testing skill do?

When the user wants to prevent regressions, improve test coverage, or says 'add tests,' 'improve coverage,' 'we keep breaking this,' 'write regression tests,' 'characterization tests,' or after fixing a production bug to ensure it never recurs.

How do I install the Regression Testing skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add 0xranx/agentbrief --skill regression-testing. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Regression Testing popular?

It lives in 0xranx/agentbrief, which has 43 GitHub stars and 0 forks.

Related skills

Typescript Advanced Types

43

0xranx/agentbrief

Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.

Software Development

Analytics Setup

43

0xranx/agentbrief

When the user needs to set up product analytics, event tracking, or says 'set up analytics,' 'add tracking,' 'GA4,' 'Mixpanel,' 'PostHog,' 'Amplitude,' 'what events should we track,' 'conversion tracking,' 'funnel tracking,' or is launching a product and needs to instrument it for data collection.

Data & Analytics

API Documentation

43

0xranx/agentbrief

Create comprehensive API documentation for developers. Use when documenting REST APIs, GraphQL schemas, or SDK methods. Handles OpenAPI/Swagger, interactive docs, examples, and API reference guides.

Software Development

TDD

43

0xranx/agentbrief

Red-green-refactor cycle for test-driven development

Testing & QA

QA Test and Fix

43

0xranx/agentbrief

When the user wants to find and fix bugs, or says 'QA this,' 'test this,' 'find bugs,' 'why is this broken,' 'it doesn't work,' 'check for bugs,' 'smoke test,' or after any significant code change. This is the full QA cycle: discover → reproduce → diagnose → fix → verify.

Testing & QA

Visual Proof

48

frankxai/claude-skills-library

Capture before/after screenshot evidence of a web page at real breakpoints (375, 768, 1440) in both light and dark themes, using Playwright against a local dev server or a deployed URL. Use before starting any visual change to capture the current state, and again after to prove the delta. Also use when asked to "show me what it looks like", check responsive behavior, verify dark mode, or confirm a layout does not break on mobile. Reports honestly when a browser or server is unavailable rather than describing a page it never rendered.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.