skills.rest
m2ai-portfolio
m2ai-portfolioOFFICIAL
Explore all skills by this author →
GitHub

api-breaking-change-scanner

Scan codebases for deprecated API parameters and report file paths, line numbers, and remediation actions.

4|1|Updated Apr 11, 2026
Search Tags:#reporting#code-scanning#migration-planning#version-upgrade#api-migration#deprecated-parameters
One-click install
npx skills add https://github.com/m2ai-portfolio/m2ai-skills-pack --skill api-breaking-change-scanner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-breaking-change-scanner
Source: https://github.com/m2ai-portfolio/m2ai-skills-pack/tree/main/skills/api-breaking-change-scanner
Command: npx skills add https://github.com/m2ai-portfolio/m2ai-skills-pack --skill api-breaking-change-scanner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans a codebase to identify deprecated API parameters that cause hard failures (400 errors) or silent behavioral changes when migrating to a new model version, surfacing exact file and line locations along with migration actions.

Core Features & Use Cases

  • Pre-migration inventory of deprecated API parameters with suggested replacements.
  • Codebase scan across targeted file types to surface breaking patterns and references.
  • Reports detailing file paths, line numbers, and migration actions to guide engineers.

Quick Start

Run the scanner on your codebase before upgrading to a new model version to identify deprecated parameters and generate remediation guidance.

Frequently Asked Questions about api-breaking-change-scanner

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

FAQPage Schema
How do I find deprecated API parameters in a codebase before a model upgrade?▼

To find deprecated API parameters before a model upgrade, scan the codebase using a target version, repository root, and file-type filters to surface breaking patterns and generate remediation guidance.

What is the best way to prevent 400 errors during an API migration?▼

The best way to prevent 400 errors during an API migration is to run a pre-migration inventory scan that identifies deprecated parameters and reports exact file paths and line numbers for remediation.

Can I scan large repositories for silent behavioral changes when updating API versions?▼

Yes, you can scan large repositories for silent behavioral changes by applying version-specific file-type filters to surface breaking patterns and deprecated API references across the codebase.

Does the API breaking change scanner require specific inputs to detect deprecated parameters?▼

Yes, detecting deprecated parameters requires a target version, repository root, and file-type filters to accurately locate exact file paths, line numbers, and recommended migration actions.

What limitations should I expect when scanning for deprecated API parameters?▼

Scanning for deprecated API parameters is limited to the specified file types and target version provided, meaning it requires accurate version filters to correctly identify breaking patterns and remediation actions.

Related Skills

Explore More Software Engineering Skills→
alex-voloshin-devalex-voloshin-dev
2

ai-skills-init

Detect codebase type and initialize configuration scaffolding and memory directories.

Community
Advanced
float-ritual-stackfloat-ritual-stack

verify-citations

Verify citations against the codebase and produce a structured report.

Official
Advanced
motormetricsmotormetrics
21

dependency-upgrade

Automate centralized dependency upgrades across pnpm workspaces with catalog-based versioning.

Official
Advanced
Mekann2904Mekann2904

code-transform

no response

Community
Advanced