Menü
Bump library versions in gradle.properties and prepare release notes
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Quick review of the current diff for bugs, logic errors, convention violations, and test gaps
Scaffold a new feature module with the appropriate layers and MESA conventions
Scaffold a new Strata interactor with interface, implementation, fake, and test
Add a new screen to an existing feature module with StateHolder, UI, factories, and tests
Add missing test cases, targeting a specific file or all changed files on the branch
Diagnose and fix an error from a build failure, stack trace, or error message
| name | bump-version |
| description | Bump library versions in gradle.properties and prepare release notes |
| disable-model-invocation | true |
| argument-hint | <module> <major|minor|patch> OR all <major|minor|patch> |
Bump the version of one or more MESA library modules and prepare for release.
Input: $ARGUMENTS
Determine what to bump:
<module> <level> → Bump a single module (e.g., trapeze patch, strata minor)all <level> → Bump all library modulesValid modules: trapeze, trapeze-navigation, strata, trapeze-test, mesa-bom
Valid levels: major, minor, patch
If mesa-bom is not explicitly included but other modules are bumped, prompt whether the BOM version should also be bumped (it typically should for releases).
Read the gradle.properties file for each affected module:
trapeze/gradle.propertiestrapeze-navigation/gradle.propertiesstrata/gradle.propertiestrapeze-test/gradle.propertiesmesa-bom/gradle.propertiesExtract the current publishingVersion value from each.
Apply semantic versioning:
major → increment major, reset minor and patch to 0minor → increment minor, reset patch to 0patch → increment patchDisplay the version changes for confirmation:
Module Current → New
trapeze 0.2.0 → 0.2.1
trapeze-navigation 0.2.0 → 0.2.1
mesa-bom 0.2.0 → 0.2.1
Ask the user to confirm before applying.
Update the publishingVersion property in each affected gradle.properties file.
If the BOM was bumped, also verify that the BOM's dependency declarations reference the correct versions of the other modules.
Gather commits since the last release tag:
git log $(git describe --tags --abbrev=0)..HEAD --oneline to get commits since the last tagGenerate release notes grouped by category:
Format as markdown suitable for a GitHub release.
Report:
v{BOM_VERSION}