regression-testing

Evaluate bug fixes and generate regression test scaffolding.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MacroMan5/claude-code-workflow-plugins --skill regression-testing-macroman5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-testing
Source: https://github.com/MacroMan5/claude-code-workflow-plugins/tree/main/.claude/skills/regression-testing
Command: npx skills add https://github.com/MacroMan5/claude-code-workflow-plugins --skill regression-testing-macroman5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After bug fixes, this Skill decides whether to add regression tests to prevent future regressions, and can generate test scaffolding when warranted.

Core Features & Use Cases

  • Decision criteria: Severity, coverage, and complexity guide test generation.
  • Test templates: Provides scaffolding for tests with realistic examples.
  • Use Case: After a bug fix PR, determine if regression tests are necessary and add them.

Quick Start

Provide bug context and request regression tests.

Frequently Asked Questions about regression-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When should I add regression tests after a bug fix?

Regression tests prevent fixed bugs from reoccurring. Add them for critical bugs, low-coverage areas, integration boundaries, complex fixes, and recurring patterns where the fix carries reintroduction risk.

How do I decide if a bug fix needs regression testing?

Evaluate bug severity, code coverage in the affected area, and fix complexity. Critical bugs, subtle issues in under-tested code, and fixes touching integration points warrant regression tests to prevent future regressions.

Can this generate test scaffolding for my bug fixes?

Yes. This Skill generates test templates and scaffolding with realistic examples after analyzing bug context, helping you implement regression tests without building from scratch.

What's the best way to prevent regressions after code fixes?

Automated regression testing captures the bug fix scenario, ensuring the same defect won't reappear in future releases. It's especially critical for complex bugs and low-coverage code paths.

How do I use this after submitting a bug fix PR?

Provide bug context—severity, affected code area, and fix details—and request regression tests. The Skill analyzes the fix and generates test scaffolding based on coverage and complexity factors.

Does this work for all types of bugs?

It's most effective for critical bugs, subtle defects, complex fixes, and recurring issues. Simple, isolated fixes in well-tested code may not require regression testing based on decision criteria.