refactor-risk-assess

[Code Quality] Evaluates risk level of proposed refactoring changes. Use to assess dependencies, blast radius, rollback difficulty, and determine if changes are safe to proceed.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026

When & Why to Use This Skill

The Refactor Risk Assessment skill is a specialized tool designed to evaluate the safety and potential impact of proposed code changes. By systematically analyzing critical dimensions such as blast radius, reversibility, and test coverage, it provides developers with a structured framework to identify high-risk refactors, minimize technical debt, and ensure system stability during the development lifecycle.

Use Cases

  • Blast Radius Analysis: Use the skill to determine if a proposed change to a public API or shared interface will impact multiple downstream dependencies, helping to prevent accidental breaking changes.
  • Legacy Code Refactoring: Assess the risk level of modifying legacy modules with low test coverage to decide whether to proceed or prioritize adding unit tests first.
  • Rollback and Reversibility Planning: Evaluate the difficulty of reversing changes involving data migrations or external service integrations to prepare a robust contingency plan.
  • Go/No-Go Decision Making: Utilize the standardized criteria to provide objective recommendations on whether a refactoring task is safe to merge or requires further review and testing.
namerefactor-risk-assess
description"[Code Quality] Evaluates risk level of proposed refactoring changes. Use to assess dependencies, blast radius, rollback difficulty, and determine if changes are safe to proceed."

Refactor: Risk Assessment

Evaluate and mitigate risks before executing changes.

Risk Dimensions

1. Blast Radius

Level Description Example
LOW Single file, private methods Rename local variable
MEDIUM Multiple files, internal APIs Extract helper class
HIGH Public APIs, many dependents Change interface signature

2. Reversibility

Level Description
LOW RISK Git revert fixes everything
MEDIUM Requires coordinated rollback
HIGH Data migration, external deps

3. Test Coverage

Coverage Risk Impact
> 80% Safe to proceed
50-80% Add tests first
< 50% HIGH RISK

Go/No-Go Criteria

PROCEED if: Test coverage adequate, Blast radius understood, Rollback plan exists BLOCK if: Critical path no tests, Public API change without review