skills.rest
cubetribe
cubetribeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

api-change

Detect and analyze breaking changes in API schemas and backend routes.

45|7|Updated Dec 7, 2025
Search Tags:#automation#architecture#code review#api#breaking changes#impact analysis
One-click install
npx skills add https://github.com/cubetribe/ClaudeCode_GodMode-On --skill api-change
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-change
Source: https://github.com/cubetribe/ClaudeCode_GodMode-On/tree/main/skills/api-change
Command: npx skills add https://github.com/cubetribe/ClaudeCode_GodMode-On --skill api-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents production outages by automatically identifying breaking API changes and ensuring downstream consumers are updated before code is merged.

Core Features & Use Cases

  • Automated Impact Analysis: Detects modifications to critical API paths and interfaces during every write operation.
  • Breaking Change Protocol: Enforces a mandatory review process for any additive, modification, or removal changes that impact system stability.
  • Use Case: When a developer renames a field in a shared DTO, this skill triggers an analysis to identify all affected frontend and backend consumers, ensuring the change is documented and versioned correctly.

Quick Start

Ask the api-guardian to analyze the impact of the current changes on downstream consumers.

Frequently Asked Questions about api-change

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

FAQPage Schema
How do I detect breaking changes in API schemas before merging code?▼

Detect breaking API schema changes by monitoring file modifications during write operations to identify downstream consumer impact and enforce mandatory architectural review protocols before merging code.

What is API impact analysis and when do I need it for backend routes?▼

API impact analysis identifies modifications to critical API paths and interfaces, classifying changes as additive, modification, or removal to ensure proper versioning and migration strategies for backend routes.

How to automate code review for breaking API modifications in shared DTOs?▼

Automate code review for shared DTOs by triggering an analysis upon field renames to identify all affected frontend and backend consumers, ensuring modifications are documented and versioned correctly.

Can I enforce a mandatory review process for downstream consumer impact?▼

Yes, you can enforce a mandatory review process by validating API integrity and triggering a breaking change protocol for any additive, modification, or removal changes that impact system stability.

Does automated breaking change detection work with interface definitions and schemas?▼

Yes, automated breaking change detection works by analyzing interface definitions and schemas, classifying modifications, and enforcing architectural review to prevent production outages from unupdated downstream consumers.

What is the best way to classify API changes for proper versioning and migration?▼

The best way to classify API changes for versioning and migration is to validate API integrity by categorizing modifications as additive, modification, or removal, ensuring proper migration strategies are enforced.

Related Skills

Explore More Software Engineering Skills→
genesis-agentsgenesis-agents
2

Schema Architect

Define system architecture schemas, ADRs, and cross-module interfaces.

Community
Advanced
xtrm-devxtrm-dev
4

gitnexus-pr-review

Map PR diffs to execution flows and identify merge risks.

Official
Intermediate
ek33450505ek33450505
8

freeze-mode

Restrict tools to read-only operations during analysis sessions.

Community
Basic
platyplusplatyplus

evolve

Manage Cairn schema migrations with dry-run previews and confirmations.

Official
Advanced