code-breaking-changes

Detects breaking changes across app-server APIs, CLI parameters, configuration loading, and session resumption.

Updated Aug 4, 2026
One-click install
npx skills add https://github.com/sjc786526-coder/RONDO --skill code-breaking-changes-sjc786526-coder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-breaking-changes
Source: https://github.com/sjc786526-coder/RONDO/tree/main/multidev/.codex/skills/code-review-breaking-changes
Command: npx skills add https://github.com/sjc786526-coder/RONDO --skill code-breaking-changes-sjc786526-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes can silently break external integration surfaces such as app-server APIs, CLI parameters, configuration loading, and session resumption from existing rollouts. This Skill systematically reviews a codebase for all possible breaking changes instead of stopping after the first issue found. ## Core Features & Use Cases - API Surface Review: Inspects app-server APIs for incompatible signature, schema, or behavior changes. - CLI and Config Compatibility: Checks CLI parameters and configuration loading paths for changes that would break existing invocations or config files. - Session Continuity Checks: Verifies that resuming sessions from existing rollouts still works after code modifications. - Use Case: Before merging a pull request in a CLI tool repository, run this Skill to enumerate every way the change could break downstream consumers, existing configs, or in-flight sessions. ## Quick Start Review the current code changes and list all possible breaking changes across the app-server APIs, CLI parameters, configuration loading, and session resumption.

Frequently Asked Questions about code-breaking-changes

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

FAQPage Schema
How do I check for breaking changes before merging a pull request?▼

Run a breaking-change review that inspects all external integration surfaces, including app-server APIs, CLI parameters, configuration loading, and session resumption. The review enumerates every possible breakage mode rather than stopping at the first issue.

What surfaces should a breaking change review cover in a CLI tool?▼

A thorough review covers app-server APIs, CLI parameter parsing, configuration file loading, and the ability to resume sessions from existing rollouts. Changes to any of these can break downstream consumers or existing user setups.

Can code changes break resuming sessions from existing rollouts?▼

Yes. Changes to session serialization formats, state schemas, or rollout storage can prevent resuming previously saved sessions. This Skill explicitly checks session resumption paths as part of its breaking-change analysis.

Why does a breaking change review need to find all issues instead of one?▼

Breaking changes often cluster across multiple surfaces, so stopping after the first finding leaves consumers exposed. This Skill is explicitly instructed to analyze all possible ways breaking changes can occur before concluding.

What are the limitations of automated breaking change detection?▼

Detection relies on reasoning over code diffs and integration surfaces, so behavioral changes without signature changes may be missed. It works best as a complement to compatibility test suites and manual API review.