skills.rest
Burburton
BurburtonCOMMUNITY
Explore all skills by this author →
GitHub

Regression Checklist

Guide regression testing with a systematic checklist for code changes.

2|Updated Mar 14, 2026
Search Tags:#testing#quality assurance#code review#checklist#regression#risk assessment
One-click install
npx skills add https://github.com/Burburton/amazingteam --skill regression-checklist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Regression Checklist
Source: https://github.com/Burburton/amazingteam/tree/main/.ai-team/skills/regression-checklist
Command: npx skills add https://github.com/Burburton/amazingteam --skill regression-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents unintended side effects and regressions by providing a structured checklist to verify the impact of code changes across different areas of the application.

Core Features & Use Cases

  • Comprehensive Verification: Guides users through checking core functionality, affected areas, neighboring modules, and edge cases.
  • Risk Assessment: Provides a matrix to understand the risk level associated with different change types and suggests appropriate testing.
  • Use Case: Before merging a pull request that modifies a critical API, use this Skill to systematically ensure that all dependent services and user-facing features remain unaffected.

Quick Start

Run the regression checklist to verify the impact of the latest code changes.

Frequently Asked Questions about Regression Checklist

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

FAQPage Schema
How do I ensure code changes do not introduce unintended side effects?▼

To prevent unintended side effects, apply a systematic regression testing checklist that verifies core functionality, affected areas, and neighboring modules. This structured approach validates code changes and ensures application stability before deployment.

What is the best way to perform regression testing before merging a pull request?▼

The best way to perform regression testing is using a comprehensive validation checklist that identifies change scope, verifies dependent services, and checks edge cases. A risk assessment matrix helps determine appropriate testing depth for different change types.

How do I assess the risk level of different code change types?▼

Assess code change risk using a risk assessment matrix that categorizes change types and suggests appropriate testing levels. This matrix helps identify which modifications require deeper verification of core and affected functionalities.

What should a code review checklist cover for quality assurance?▼

A thorough code review checklist for quality assurance should cover change scope identification, core functionality verification, neighboring module checks, edge case analysis, and non-functional requirements to ensure comprehensive validation.

Related Skills

Explore More Software Engineering Skills→
Srain021Srain021

kestrel-mcp-audit-codebase

Audits codebases for gaps, risks, dead code, and non-idiomatic patterns via a structured workflow.

Community
Advanced
xxihxxih
1

quality-verify

Run verification commands and record results in .quality/quality-check.md.

Community
Intermediate
wojonswojons
4

testing-unit

Execute unit tests across programming languages and testing frameworks.

Community
Basic
grasberggrasberg
3

ml-ops-engineer

Coordinate ML model lifecycles from notebook to production deployment.

Community
Advanced