version-breaking-change-guard

Scans codebase to quantify affected files and calls for API changes.

Updated Jan 6, 2026

Search Tags:#risk-assessment #impact-analysis #breaking-change #migration-plan #codebase-scan #api-consumers

Ready to run

npx skills add https://github.com/cslsoftwares/ParamentersORM --skill version-breaking-change-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: version-breaking-change-guard
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/version-breaking-change-guard_V1.0.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill version-breaking-change-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and quantify the impact of breaking changes to public APIs before they are applied, helping teams avoid widespread regressions and deployment surprises.

Core Features & Use Cases

Automated impact scan across src, tests, and docs to locate all consumers of the affected API.
Quantifies impact by counting files, call sites, and usage contexts, and provides a risk ranking.
Generates a concrete migration plan with concrete steps and requires human approval before applying changes.
Produces a shareable report for stakeholders.

Quick Start

Provide the API change details to the guard to generate an impact report.

Frequently Asked Questions about version-breaking-change-guard

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

FAQPage Schema

How do I assess the impact of breaking changes before shipping an API update?▼

Impact analysis for breaking changes works by scanning your repository to locate all API consumers, counting affected files and call sites, and producing a structured report with a risk ranking to guide safe deployment.

How do I generate a migration plan for breaking API changes?▼

Generating a migration plan involves scanning the entire repository for API consumers and producing concrete, step-by-step migration instructions for each affected file and call site.

Can I automate codebase scanning to find all API consumers before a major update?▼

Yes, you can automate codebase scanning to search across source, tests, and docs to locate all API consumers and quantify usage contexts before applying breaking changes.

Does the breaking-change migration process require human approval?▼

Yes, the breaking-change migration process requires explicit human approval prior to applying any modifications, ensuring developers review the impact report before proceeding.

What is the best way to quantify risk for public API breaking changes?▼

Quantifying risk for breaking changes involves counting affected files, call sites, and usage contexts during a codebase scan to produce a structured risk ranking and shareable stakeholder report.