Bug Regression Preventer logo

Bug Regression Preventer

Community
dykyi-roman
bug-regression-preventer

Regression prevention checklist for bug fixes. Ensures API compatibility, behavior preservation, and no unintended side effects.

Overview

Publisherdykyi-roman
Repositoryawesome-claude-code
Skill namebug-regression-preventer
Stars
98
Forks
25
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by dykyi-roman on GitHub. Read the source before you install it.

Installation

Install the Bug Regression Preventer AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/dykyi-roman/awesome-claude-code.git /tmp/awesome-claude-code
mkdir -p .claude/skills
cp -r /tmp/awesome-claude-code/skills/bug-regression-preventer .claude/skills/bug-regression-preventer
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Bug Regression Preventer in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Bug Regression Preventer on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Bug Regression Preventer is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Bug Regression Preventer

Systematic checklist to ensure bug fixes don't introduce new problems.

Pre-Fix Checklist

1. Reproduction Verification

  • Bug can be consistently reproduced
  • Reproduction steps documented
  • Environment conditions noted
  • Expected vs actual behavior clear

2. Test Coverage Check

  • Existing tests identified
  • Missing test cases noted
  • Flaky tests identified
  • Performance benchmarks available (if relevant)

3. Impact Assessment

  • Callers identified
  • Dependents mapped
  • Events/messages reviewed
  • API contracts reviewed

Fix Validation Checklist

API Compatibility

Method Signature
php
// BEFORE
public function process(Order $order): OrderResult

// AFTER - Must maintain compatibility
public function process(Order $order): OrderResult  // ✓ Same signature
public function process(Order $order): Result       // ✗ Return type changed
public function process(Order $order, bool $flag): OrderResult // ✗ New required param
public function process(Order $order, bool $flag = false): OrderResult // ✓ Optional param OK

Checklist:

  • Return type unchanged
  • Parameter types unchanged
  • Parameter order unchanged
  • No new required parameters
  • No removed parameters
Exception Contract
php
// BEFORE - throws ValidationException
public function validate(Data $data): void

// AFTER - Must throw same or subtype
public function validate(Data $data): void  // throws ValidationException ✓
public function validate(Data $data): void  // throws DataValidationException extends ValidationException ✓
public function validate(Data $data): void  // throws RuntimeException ✗ Different hierarchy

Checklist:

  • Same exception types thrown
  • New exceptions are subtypes of existing
  • Exception messages format preserved (if parsed downstream)
  • Exception codes unchanged (if used)

Behavior Preservation

Return Value Semantics
php
// BEFORE
public function findUser(UserId $id): ?User
// Returns null for non-existent user

// AFTER - Preserve null semantics
public function findUser(UserId $id): ?User
// Must still return null for non-existent user
// NOT throw NotFoundException (behavior change)

Checklist:

  • Null return preserved (if applicable)
  • Empty collection return preserved (if applicable)
  • Default values unchanged
  • Error conditions unchanged
Side Effects
php
// BEFORE - Has side effects
public function completeOrder(Order $order): void
{
    $order->complete();                    // 1. State change
    $this->repository->save($order);       // 2. Database write
    $this->events->publish($event);        // 3. Event published
}

// AFTER - Must preserve all side effects
// Unless the bug IS one of these side effects

Checklist:

  • State changes preserved
  • Database writes preserved
  • Events still published
  • Messages still sent
  • Logs still written
  • Metrics still recorded

Data Integrity

Database Schema
  • No schema changes required
  • Existing data remains valid
  • Indexes still effective
  • Constraints not violated
Data Format
php
// BEFORE - stored as "2024-01-15"
// AFTER - must stay "2024-01-15"
// NOT "2024-01-15T00:00:00Z" (format change)

Checklist:

  • Serialization format unchanged
  • JSON structure unchanged
  • Date/time formats unchanged
  • Numeric precision unchanged

Performance

Query Patterns
  • No new N+1 queries
  • No removed indexes usage
  • No added full table scans
  • Transaction scope unchanged
Resource Usage
  • Memory usage not increased significantly
  • CPU usage not increased significantly
  • Network calls not increased
  • File I/O not increased

Test Requirements

Mandatory Tests

1. Reproduction Test
php
/**
 * This test reproduces the original bug.
 * It MUST fail before the fix and pass after.
 */
#[Test]
public function testBugReproduction(): void
{
    // Arrange: Set up conditions that trigger the bug
    $order = OrderBuilder::create()
        ->withItem(null) // The bug trigger
        ->build();

    // Act & Assert: Verify bug is fixed
    $result = $this->service->calculateTotal($order);

    // Before fix: throws NullPointerException
    // After fix: returns Money::zero()
    $this->assertEquals(Money::zero('USD'), $result);
}
2. Edge Case Tests
php
#[Test]
public function testEdgeCases(): void
{
    // Test boundary conditions around the fix
    $this->assertEquals($expected, $this->service->process($emptyInput));
    $this->assertEquals($expected, $this->service->process($maxInput));
    $this->assertEquals($expected, $this->service->process($nullableInput));
}
3. Regression Tests
php
#[Test]
public function testExistingBehaviorPreserved(): void
{
    // Test that normal cases still work
    $normalOrder = OrderBuilder::create()
        ->withItem($validItem)
        ->build();

    $result = $this->service->calculateTotal($normalOrder);

    $this->assertEquals($expectedTotal, $result);
}

Test Coverage Matrix

ScenarioBefore FixAfter FixTest Required
Bug trigger caseFails/crashesWorks correctly✓ Reproduction
Normal caseWorksMust still work✓ Regression
Edge casesMay varyDefined behavior✓ Edge case
Related featuresWorkMust still work✓ Integration

Common Regression Patterns

1. Over-Fixing

php
// Bug: Null pointer when item is null
// WRONG: Remove null items entirely (behavior change)
$items = array_filter($items, fn($i) => $i !== null);

// CORRECT: Handle null gracefully
foreach ($items as $item) {
    if ($item === null) {
        continue; // Skip null, preserve others
    }
    // ... process item
}

2. Breaking Callers

php
// Bug: Method should return early for invalid state
// WRONG: Change return type
public function process(): void // Was: ?Result

// CORRECT: Return null for invalid state (preserve contract)
public function process(): ?Result
{
    if (!$this->isValid()) {
        return null;
    }
    // ...
}

3. Hiding Errors

php
// Bug: Exception crashes application
// WRONG: Swallow exception
try {
    $this->service->process($data);
} catch (Exception $e) {
    // Silent failure - bug hidden
}

// CORRECT: Handle specific exception appropriately
try {
    $this->service->process($data);
} catch (ValidationException $e) {
    return Result::invalid($e->getErrors());
}

4. Performance Regression

php
// Bug: Missing validation
// WRONG: Add validation that queries database in loop
foreach ($items as $item) {
    if (!$this->repository->exists($item->getId())) { // N+1 query!
        throw new NotFoundException();
    }
}

// CORRECT: Batch validation
$ids = array_map(fn($i) => $i->getId(), $items);
$existing = $this->repository->findByIds($ids);
if (count($existing) !== count($items)) {
    throw new NotFoundException();
}

Post-Fix Verification

Manual Testing

  • Bug no longer reproducible manually
  • Normal workflows still work
  • Edge cases handled correctly
  • Error messages appropriate

Automated Testing

  • All unit tests pass
  • All integration tests pass
  • All E2E tests pass
  • No new test failures

Code Review Points

  • Fix is minimal (only affected code changed)
  • No unrelated changes
  • No commented-out code
  • No debug statements left
  • Proper exception handling
  • No new code smells

Documentation

  • PHPDoc updated if public API affected
  • CHANGELOG entry added
  • Issue linked in commit
  • Breaking changes documented (if any)

Rollback Plan

Before Deployment

  1. Tag current version: git tag pre-fix-{issue-id}
  2. Document rollback command: git revert {commit-hash}
  3. Identify monitoring dashboards
  4. Set alert thresholds

Monitoring After Deployment

  • Error rates normal
  • Latency normal
  • Resource usage normal
  • No new exception types
  • Business metrics stable

Rollback Triggers

  • Error rate increase > 5%
  • Latency increase > 20%
  • New critical errors appearing
  • Business metric anomaly

Quick Checklist Summary

markdown
## Pre-Fix
- [ ] Bug reproduced
- [ ] Impact assessed
- [ ] Existing tests identified

## Fix Applied
- [ ] API compatible
- [ ] Behavior preserved
- [ ] Side effects intact
- [ ] Data integrity maintained

## Tests Added
- [ ] Reproduction test
- [ ] Edge case tests
- [ ] Regression tests

## Post-Fix
- [ ] All tests pass
- [ ] Code reviewed
- [ ] Documentation updated
- [ ] Monitoring ready

Frequently asked questions

What does the Bug Regression Preventer AI skill do?

Regression prevention checklist for bug fixes. Ensures API compatibility, behavior preservation, and no unintended side effects.

Why use Bug Regression Preventer on TypingMind?

Because you install it once and use it with any model. Bug Regression Preventer is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Bug Regression Preventer in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/dykyi-roman/awesome-claude-code/tree/master/skills/bug-regression-preventer. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Bug Regression Preventer?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Bug Regression Preventer?

As many as you like. As long as a model supports skills, you can use Bug Regression Preventer with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Bug Regression Preventer AI skill free?

Yes. It is published on GitHub by dykyi-roman under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇