skills.rest
looooonk
looooonkCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-breaking-changes

Detects breaking changes across APIs, CLI parameters, configuration, and session resumption.

5|1|Updated Jun 26, 2026
Search Tags:#code review#cli#configuration#breaking changes#session resumption#api compatibility
One-click install
npx skills add https://github.com/looooonk/better-codex --skill code-breaking-changes-looooonk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-breaking-changes
Source: https://github.com/looooonk/better-codex/tree/main/.codex/skills/code-review-breaking-changes
Command: npx skills add https://github.com/looooonk/better-codex --skill code-breaking-changes-looooonk

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 code for these breaking changes so they are caught before release. ## Core Features & Use Cases - API Surface Review: Searches for breaking changes in app-server APIs that external consumers depend on. - CLI and Configuration Analysis: Detects changes to CLI parameters and configuration loading that could break existing user setups. - Session Compatibility Checks: Verifies that sessions can still be resumed from existing rollouts after code changes. - Use Case: Before merging a pull request that modifies the CLI argument parsing or config schema, run this Skill to enumerate every way the change could break existing integrations rather than stopping at the first issue found. ## Quick Start Review this pull request for breaking changes across 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 a pull request for breaking changes?▼

Review all external integration surfaces the change touches, including app-server APIs, CLI parameters, configuration loading, and session resumption. Analyze every possible breaking path rather than stopping after finding the first issue.

What counts as a breaking change in a CLI tool?▼

Breaking changes include removed or renamed CLI parameters, changed configuration loading behavior, incompatible API responses, and rollouts that can no longer be resumed. Any change that breaks existing consumers or saved state qualifies.

Can configuration changes break existing users?▼

Yes. Changes to configuration loading, such as renamed keys, altered defaults, or removed options, can break existing user setups even when the code itself compiles and passes tests.

Why does session resumption break after an update?▼

Session resumption breaks when the rollout format or serialization changes without backward compatibility. Existing saved rollouts may fail to load if the new code cannot parse the old session state.

What are the limitations of automated breaking change detection?▼

Detection depends on identifying all external integration surfaces, which requires knowledge of how consumers use the APIs and CLI. Subtle behavioral changes without signature changes may still require manual review.

Related Skills

Explore More Software Engineering Skills→
bilacchibilacchi

review

Reviews git diffs against coding standards and spec requirements using parallel sub-agents.

Community
Intermediate
cslsoftwarescslsoftwares

version-orchestrator

Coordinate semver bumps, deprecations, migrations, and release notes across environments.

Community
Advanced
wesleyosantos91wesleyosantos91
6

contract-review

Evaluate API and data contracts for breaking changes and compatibility.

Community
Intermediate
jeremydhoover-blipjeremydhoover-blip
7

diffing-and-versioning-context-packs

Compare context pack versions and generate semantic diff reports.

Community
Intermediate