// Use this skill to automate a new version release for the juriscraper project. Trigger by asking to "release a new version" or "bump version."
| name | juriscraper-release |
| description | Use this skill to automate a new version release for the juriscraper project. Trigger by asking to "release a new version" or "bump version." |
| argument-hint | [patch|minor|major] |
| disable-model-invocation | true |
| allowed-tools | Bash, Read, Edit, Write, Glob, Grep |
You are an expert at managing the juriscraper release process. When this skill is active, follow these steps exactly:
main is up-to-date with remote. Pull if necessary. Abort if there are uncommitted changes that conflict with the pull.$ARGUMENTS (defaults to patch if not specified). Examples: if current is 2.1.0, then patch โ 2.1.1, minor โ 2.2.0, major โ 3.0.0. If the bump is minor or major, show the user the current and new version and ask for confirmation before proceeding.version-bump-v{version_number}.version in pyproject.toml.uv sync.## {version_number} - {YYYY-MM-DD}. Reset the "Coming up" bullet points to empty:
Features:
-
Changes:
-
Fixes:
-
pre-commit run --all-files. If it fails, attempt to fix and re-run once.pyproject.toml, CHANGES.md, and uv.lock.version bump v{version_number}.v{version_number}.gh pr create). Use the user signature; do not co-author the commits. Use the following PR format:
version bump v{version_number}## Summary
- Bump version from {old_version} to {version_number}
git push --tags command so the user can decide to trigger the final release.uv for dependency management.