Analyze code changes for regression risks and enforce approval gates.
npx skills add https://github.com/Doumajnik/template --skill change-pipeline
Please help me install this Agent Skill. Skill: change-pipeline Source: https://github.com/Doumajnik/template/tree/main/.github/skills/change-pipeline Command: npx skills add https://github.com/Doumajnik/template --skill change-pipeline
Modifying existing code carries high risk of unintended regressions, broken dependent functionality, and cascading side effects even for seemingly small changes. This Skill eliminates that risk by enforcing a structured, adversarial pipeline that maps blast radius and validates every change before implementation.
Use the change-pipeline skill to update the existing user authentication flow to add multi-factor authentication support without breaking existing login integrations.
High-intent search queries and answers about installing and using this skill.
To safely modify existing source code without causing regressions, use a structured change pipeline that enforces mandatory impact analysis, adversarial review, and regression checklists before implementation. This maps the blast radius and validates backward compatibility to prevent broken dependent functionality.
The best way to refactor a core module and prevent breaking dependent functionality is to apply an adversarial review pipeline that automatically maps all affected files and dependent modules. This process uses explicit regression checklists and user approval gates to validate changes before they are implemented.
Impact analysis for brownfield development feature updates works by automatically mapping all affected files, dependent modules, and potential regression risks before any code is touched. This structured analysis identifies cascading side effects and enforces user approval gates to ensure change safety.
Yes, you can update API signatures in an existing project without breaking backward compatibility by enforcing a change pipeline with dedicated critique loops and regression checks. This governance workflow validates all dependent integrations and requires explicit user approval before implementation proceeds.
You need a structured change pipeline for code alterations when modifying existing source code carries a high risk of unintended regressions or cascading side effects. It is essential for brownfield development tasks including feature updates, refactoring, logic adjustments, and API signature changes.
Modifying existing code causes unintended side effects and broken functionality because even seemingly small changes can have a large blast radius across dependent modules. A change pipeline eliminates this risk by mapping affected files and enforcing regression checklists before implementation begins.
jamon8888Rename, extract, and restructure code with dependency impact analysis.
cslsoftwaresMap public consumers and enforce compatibility decisions before renaming symbols.
hieuckRun sandbox-mode Vitest regression tests for Next.js API routes.
ArabelaTsoDetect design smells in Python codebases via static AST analysis.
