Migration Guard

Detect breaking code changes in git diffs before merging.

1|Updated Mar 7, 2026

Search Tags:#code review #refactoring #api #validation #migration #breaking changes

Ready to run

npx skills add https://github.com/jimmymalhan/codereview-pilot --skill migration-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Migration Guard
Source: https://github.com/jimmymalhan/codereview-pilot/tree/main/.claude/skills/migration-guard
Command: npx skills add https://github.com/jimmymalhan/codereview-pilot --skill migration-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents accidental merging of code that introduces breaking changes by identifying issues like renamed exports, altered API signatures, or removed fields before they impact production.

Core Features & Use Cases

Breaking Change Detection: Identifies modifications to exported functions, API routes, and data schemas.
Impact Analysis: Lists files and modules that consume changed exports, highlighting potential breakage.
Use Case: Before merging a backend change that modifies a critical API endpoint, this Skill analyzes the diff, identifies all services that call the endpoint, and flags it as a breaking change requiring a migration plan.

Quick Start

Run the migration guard skill on the current git diff for the src directory.

Frequently Asked Questions about Migration Guard

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

FAQPage Schema

How do I detect breaking changes in API signatures before merging code?▼

To detect breaking changes in API signatures before merging, analyze git diffs alongside current exported symbols. This identifies altered API routes and lists consuming modules, ensuring backward compatibility or blocking the merge pending a migration plan.

What is the best way to prevent accidental merging of removed fields and renamed exports?▼

Preventing accidental merging of removed fields and renamed exports requires an automated impact analysis of git diffs. This process flags missing schema fields and maps changed exports to their consumers, mandating a migration plan if breakage is found.

How does impact analysis identify consumers of altered database schema modifications?▼

Impact analysis identifies consumers of altered database schemas by analyzing current exported symbols and file paths against the git diff. It cross-references these modifications to highlight specific files and modules that call the changed exports.

Can I validate backward compatibility for a specific source directory git diff?▼

You can validate backward compatibility by running an automated guard on the git diff for your source directory. It analyzes file paths and exported symbols to detect breaking changes, ensuring modifications do not disrupt existing API consumers.

When do I need to mandate a migration plan for changed API routes?▼

A migration plan is mandated for changed API routes when automated diff analysis detects breaking modifications to exported functions or data schemas. This ensures backward compatibility is preserved or explicitly addressed before code merging.