Menú
Bump library version in VERSION file and prepare release notes
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Add a new screen to an existing feature module with Store, UI, factories, and tests
Add missing test cases, targeting a specific file or all changed files on the branch
Thorough pre-merge audit — dependency graph, correctness, conventions, security, test coverage, and improvement suggestions
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
| name | bump-version |
| description | Bump library version in VERSION file and prepare release notes |
| disable-model-invocation | true |
| argument-hint | <major|minor|patch> |
Bump the MESA library version and prepare for release.
Input: $ARGUMENTS
Determine what to bump:
major → increment major, reset minor and patch to 0minor → increment minor, reset patch to 0patch → increment patchIf no level is provided, ask the user which bump type they want.
Read the VERSION file at the repository root to get the current version string.
Apply semantic versioning and display the version change for confirmation:
Current → New
0.2.0 → 0.3.0
Ask the user to confirm before applying.
Update the VERSION file with the new version string.
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{VERSION} (e.g., v0.3.0)draft-release.ymlpublish-release.yml will validate the package on release publish