Change-to-Regression Workflow

Use this Skill to select explainable regression scope from a change and its risk.

Skill attributes

Quality workflowTesting workflowWorkflow Skill

Call this SkillCommand

@skill change-to-regression

Enter this command in Codex to start.

StatusStable

TypeWorkflow Skill

DomainQuality workflow

SDLCTesting workflow

Good forQA / PM

LanguageChinese / English

EvalsEvals ✓

Synced2026-11-06

Why this Skill

It turns this Skill's method into a quality input that can be executed, reviewed, and reused.

Use this Skill when its method fits the current quality task.

When to use

Use this Skill

Use this Skill when its method fits the current quality task.

Common pitfalls

No content is available for this Skill yet.

Input

Minimum Input

The current scope, available context, constraints, and evidence.

Recommended Input

Project goal
Test scope
Constraints

Optional Context

Relevant code or configuration
Historical results
Logs and metrics

Output

The output follows this Skill's method and makes facts, assumptions, risks, and next steps explicit.

These are the Skill's expected output requirements, not evidence that it ran in a real project.

01An actionable result that distinguishes facts, assumptions, risks, and next steps.

Install & Quick Start

Install command / SHELL

npx skills add \
  https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-workflows/change-to-regression
  -g

change-to-regression.prompt

@skill change-to-regression

Using the current project context, produce an actionable result following this Skill.

Additional context:
[Paste project context or requirement]

---
name: change-to-regression
description: Use this skill when you need to select explainable regression scope from a change and its risk; triggers include change-to-regression, 变更回归, and Change-to-Regression Workflow.
license: PolyForm-Noncommercial-1.0.0
metadata:
  version: "1.0.0"
  compatibility: ""
  author: "Awesome QA Skills contributors"
  language: "en"
  category: "testing-workflows"
  source: "https://github.com/naodeng/awesome-qa-skills"
  license-url: "https://polyformproject.org/licenses/noncommercial/1.0.0"
---

# Change-to-Regression Workflow

## When to Use

Use this Skill to select explainable regression scope from a change and its risk.

## Output Format Options

Default to Markdown with a required/deferred/excluded regression table. If JSON is requested, preserve the prompt's separate facts, inferences, plans, execution states, and sources.

## Core constraints

Compose existing specialist Skills without copying their analysis rules. Mark host installation `UNKNOWN` without evidence. Do not report plans or static analysis as executed results. Read-only by default; external writes require authorization.

## How to Use

Read `prompts/change-to-regression.md` first; validate inputs, complete each stage, preserve sources, and return risk and handoff details. Use `README.md` for invocation examples and FAQ.

## Reference Files

- `prompts/change-to-regression.md`: full workflow, coverage, output, and recovery rules.
- `README.md`: usage examples and FAQ.
- `evals/`: trigger and behavior regression cases.

## Before delivery

- [ ] Input scope and assumptions are explicit
- [ ] Handoffs preserve sources, status, and gaps
- [ ] Execution evidence is separate from plans
- [ ] Next steps and permission boundary are clear

## Common Pitfalls

Do not invent input, assume dependencies are installed, or present recommendations as execution or approval.

## Best Practices

Provide exact base/head SHA, the full diff, test runtimes, and environment limits. After execution, attach its time, Commit, and run record.