code-breaking-changes

Name: code-breaking-changes
Availability: InStock
Author: Mithran

Detect breaking changes in APIs, CLI parameters, and configuration files.

Updated Aug 23, 2026

Search Tags:#code review #breaking changes #api monitoring #configuration analysis #session resumption

Ready to run

npx skills add https://github.com/mithran-hq/aegis-code --skill code-breaking-changes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-breaking-changes
Source: https://github.com/mithran-hq/aegis-code/tree/main/.codex/skills/code-review-breaking-changes
Command: npx skills add https://github.com/mithran-hq/aegis-code --skill code-breaking-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps detect and analyze breaking changes in external interfaces and configurations to ensure system stability.

Core Features & Use Cases

Change Detection: Find breaking modifications in app-server APIs, CLI parameters, and configuration files.
Impact Analysis: Assess how changes could affect ongoing sessions and system compatibility.
Use Case: Developers can run this Skill to verify if recent updates introduce breaking issues before deployment.

Quick Start

Use the code-breaking-changes Skill to scan your latest codebase for integration surface modifications.

Frequently Asked Questions about code-breaking-changes

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

FAQPage Schema

How do I detect breaking changes in API surfaces and configurations?▼

To detect breaking changes in API surfaces and configurations, you can analyze your codebase for modifications in app-server APIs, CLI parameters, and session resumption points to ensure system compatibility.

What is API breaking change analysis and when do I need it?▼

API breaking change analysis is the static review of code and configuration files to find incompatible modifications. You need it before deploying updates to prevent disrupting ongoing sessions and external integrations.

Does code review for breaking changes require any external dependencies?▼

No, performing a code review for breaking changes requires no external dependencies. It relies entirely on static analysis of your existing code and configuration files to detect disruptive integration modifications.

How do I assess the impact of configuration file changes on system stability?▼

You assess the impact of configuration file changes on system stability by scanning your software projects for incompatible modifications that could affect ongoing sessions and overall system compatibility.

What is the best way to find breaking modifications in session resumption points?▼

The best way to find breaking modifications in session resumption points is to run a static analysis across your codebase to identify disruptive changes in external interfaces before deployment.