Skip to content

Skill

Reviewing Regression Risk

Identifies what a specific code, API, schema, configuration, dependency, integration, or runtime-behavior change could break.

Back to Skills

When to use

Identifies what a specific code, API, schema, configuration, dependency, integration, or runtime-behavior change could break - directly affected behavior, adjacent flows, interface and contract risks, shared state, backward compatibility, permissions, error handling, and data validation - and prioritizes where verification should focus.

  • Use when

    Use when assessing the regression risk of a diff, pull request, or described change.

  • Limits

    Does not review test coverage, write tests, create patches, or produce a change set.

Skill package

SKILL.md

This Skill is a single file. The download is its SKILL.md, with the complete frontmatter and instructions.

  • reviewing-regression-risk/SKILL.md

Inputs required

Change summary
What changed, why, and which area may be affected.
Changed files or excerpts
Code, configuration, schema, API contract, dependency, or integration changes.

Access needed

Needs the change itself (a diff, changed files, or a git repository with read access) and read access to related code for tracing callers. No network access required. Read-only; does not modify files.