Agent skill · software engineering · jeremylongshore
maintainx-upgrade-migration
Migrate MaintainX API versions and handle breaking changes.
Why this skill is useful
Provides a detailed migration strategy with specific code examples for handling MaintainX API version upgrades and breaking changes.
What it needs
Requires npm installed locally. Requires maintainx account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
MaintainX Upgrade & Migration Current State !npm list 2>/dev/null head -20 Overview Handle MaintainX API version upgrades, deprecations, and breaking changes with a safe, incremental migration strategy. Prerequisites Existing MaintainX integration Test environment with separate API key Version control (git) for all integration code Instructions Step 1: Audit Current API Usage Step 2: Version Compatibility Layer Step 3: Feature Flag Migration Step 4: Migration Tests Step 5: Rollback Procedure Output API usage audit report listing all endpoints and call sites Version compatibility layer with request/response adapters Feature flag system for incremental per-endpoint migration Migration tests verifying v1/v2 equivalence Rollback procedure for safe revert Error Handling Issue Cause Solution ------- ------- ---------- 404 on v2 endpoint Endpoint path changed Update adapter mappings Field missing in v2 response Breaking schema change Add field mapping in transformResponse Mixed v1/v2 data in DB Partial migration state Run reconciliation to normalize Feature flag stuck Config not reloaded Restart service or use dynamic config Resources MaintainX API Reference Strangler Fig Pattern -- Incremental migration strategy Next Steps For CI/CD integration, see maintainx-ci-integration. Examples Dual-write during migration (write to both v1 and v2):
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/maintainx-upgrade-migration--46a017