- Home
- Skills
- Agents & Orchestration
- Enum Evolution Contract Repair
More screenshots
Works with the AI Agents you already use
Enum Evolution Contract Repair
Repair enum and status evolution drift across schemas, generated clients, serializers, UI, analytics, tests, and mixed-version consumers.
$1
Enum Evolution Contract Repair
Example session with this skill installed
I have a TypeScript monorepo with a Node API, Prisma/PostgreSQL, generated OpenAPI clients, React, and background jobs. We added PARTIALLY_REFUNDED to the OrderStatus enum. Prisma and the API schema know about it, but one generated client is stale, two frontend switches throw on unknown values, analytics maps unknown statuses to FAILED, an old worker fixture still assumes four values, and the migration note says older app versions may remain during rollout. Repair the enum evolution contract across the repository. Add deterministic local tests for mixed versions and unknown values. Do not query production, change existing order rows, deploy, or decide what PARTIALLY_REFUNDED should mean to the business.
- Read your context and instructions
- Compiled the enum evolution contract
Enum evolution drift found. The repository has a stale generated client, two closed-world UI switches, unsafe analytics coercion, and incomplete mixed-version coverage. The repair regenerates the client, adds explicit unknown-value handling, preserves existing serialized values, updates fixtures, and adds compatibility tests. Business meaning and deployed compatibility remain human-owned and unverified.
Connects securely to your tools. The creator never sees your data.
About this skill
Enum changes are deceptively small: one new status can break generated clients, exhaustive UI switches, protobuf consumers, analytics mappings, fixtures, migrations, and old application versions.
Enum Evolution Contract Repair gives an AI coding agent a disciplined repository workflow for finding every representation of an enum or discriminator, freezing stable wire identifiers, detecting unsafe unknown-value fallbacks, regenerating derived artifacts, and building mixed-version compatibility tests.
It is especially useful for OpenAPI/GraphQL clients, protobuf or event schemas, ORM/database enums, frontend status renderers, mobile clients, analytics mappings, warehouse allowlists, mocks, golden files, and rollout documentation.
The skill does not publish schemas, rewrite production data, deploy, or invent the business meaning of new statuses. It keeps those decisions with authorized owners while making the repository mechanically safer.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.
Repairs repository-level enum compatibility only. It cannot prove every external consumer is upgraded, publish schemas, execute production migrations, rewrite live data, or decide business semantics for new or retired values.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 months ago
Permissions
Use on a clean branch or clean working tree. Supply repository files and synthetic fixtures only. Keep production credentials, schema-registry tokens, customer data, and private keys out of the workspace.