@W-22934319: [API Management] Add manage-api-version Vibes skill#148
Open
taliyahhh wants to merge 2 commits into
Open
@W-22934319: [API Management] Add manage-api-version Vibes skill#148taliyahhh wants to merge 2 commits into
taliyahhh wants to merge 2 commits into
Conversation
Add command-line skill for managing API dependency versions in Mule projects. Provides natural language interface to the API Management feature in Anypoint Studio. Features: - Display current API dependency versions - Check for available updates from Exchange - Update API versions with automatic rescaffold - Multi-API batch updates - Integration with Project Properties → API Specs tab functionality This skill wraps the API Management UI (PR #3742) for CLI/AI-driven workflows. Related: - Main repo PR #3742: API Management UI implementation - API component PR #1665: POM property placeholder support Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
- Fix ---2 typo in SKILL.md body separator - Add Prerequisites section (anypoint-cli-v4 + mvn checks, install steps, note that DISPLAY paths work without CLI) - Expand API spec classifier list to the authoritative set used by the backend: raml, oas, graphql, protobuf, fat-protobuf, evented-api (was: raml, oas, zip — zip is not a valid API spec classifier) - Make otherVersions parsing concrete everywhere: each element has a version string; sort descending by semver; include jq one-liner for the CHANGE path with Python fallback - Add jq rule and Python fallback to Rules section - Add two Troubleshooting entries: CLI auth conflict (ANYPOINT_BEARER + ANYPOINT_CLIENT_ID/SECRET), empty otherVersions for single-version assets - Remove accidental nested skills/mule-development/skills/ directory - Bump package version 1.4.0 → 1.4.1 and update CHANGELOG Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
fd22c94 to
cd6bdf3
Compare
Author
|
@mlinsf ready for review! |
mlinsf
approved these changes
Jun 30, 2026
leandrogilcarrano
approved these changes
Jul 1, 2026
leandrogilcarrano
left a comment
Contributor
There was a problem hiding this comment.
All validators pass. New skill is well-structured, trigger-rich description, correct semver-sorted version selection logic, proper pom.xml backup/restore on failure, and follows established mule-development skill patterns. Minor: semver convention suggests 1.6.0 (new feature) over 1.5.1 (patch), but not a blocker.
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.
@W-22934319: [API Management] Add manage-api-version Vibes skill
Description
Adds the
manage-api-versionVibes skill for reading, checking, and updating API spec dependency versions in a Mule project. Versions are stored as<{artifactId}.version>properties inpom.xml— the same values the Anypoint Studio Project Properties → API Specs tab manages.Changes
skills/mule-development/manage-api-version/SKILL.mdwith four execution paths:mvn clean package -DskipTestsrescaffold, and pom.xml backup/restore on failure1.5.0→1.6.0and updateCHANGELOG.mdChecklist
Related Links