feat(catalog): add API Evolve (api-evolve) community extension#2479
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds the new “API Evolve” community extension to Spec Kit’s community extension catalog and the README’s Community Extensions table, making it discoverable via the repo and downstream catalog consumers.
Changes:
- Added “API Evolve (api-evolve)” to the Community Extensions table in
README.md(kept in correct alphabetical position by display name). - Added a new
api-evolveentry toextensions/catalog.community.json(kept in correct alphabetical position by extension id) and bumped the catalog’s top-levelupdated_at.
Show a summary per file
| File | Description |
|---|---|
| README.md | Adds the API Evolve row to the Community Extensions table. |
| extensions/catalog.community.json | Registers the api-evolve extension metadata and updates updated_at. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 0
…evolve # Conflicts: # extensions/catalog.community.json
mnriem
approved these changes
May 7, 2026
Collaborator
|
Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Extension Submission
Extension Name: API Evolve
Extension ID:
api-evolveVersion: 1.0.0
Author: Quratulain-bilal
Repository: https://github.com/Quratulain-bilal/spec-kit-api-evolve
Release: https://github.com/Quratulain-bilal/spec-kit-api-evolve/releases/tag/v1.0.0
Description
Managed API contract evolution for Spec-Driven Development. Detects breaking changes before they ship, enforces SemVer, orchestrates deprecations, and gates
/speckit.implementuntil contract policy is satisfied. Works across OpenAPI 3.x / Swagger 2.0, GraphQL SDL, gRPC.proto, and JSON Schema.Why this fills a gap
Spec Kit ships strong workflow scaffolding around
specify → plan → tasks → implement, but contract drift between a spec and the API the spec is supposed to govern is unmanaged today. API Evolve plugs into all five lifecycle hooks to close that gap:after_specify→ detect contract files, annotate spec with current surfaceafter_plan→ freeze immutable baseline before implementationafter_tasks→ inject[API-*]governance tasks (diff, classify, deprecate, bump)before_implement→ the gate: refuses to dispatch on undeclared breaking changes, missing version bumps, or unmet deprecation policyafter_implement→ generate consumer-facing changelog and client-impact reportCapabilities
orchestrate,detect,baseline,diff,classify,bump,deprecate,deprecation-status,gate,changelog,client-impact,releasebefore_implement)api-evolve/policy.ymlChecklist
extension.ymlmanifestREADME.mdwith installation and usage docsLICENSEfile (MIT)CHANGELOG.mdpresentextensions/catalog.community.jsonbetweenagent-assignandarchitect-previewREADME.mdupdated_atbumpedNotes for reviewers
processandRead+Writebecause the gate orchestrates state across phases and thereleasecommand updates contract version fields andCHANGELOG.md.before_implementgate can be relaxed per-feature via policy if maintainers sign off.