Release
Bump the envlit version in pyproject.toml, commit, and publish a GitHub release with handwritten notes. Usage: /release <new-version>From its SKILL.md
npx -y skills add luocfprime/envlit --skill releaseAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, as published. Nobody here has run it
Release envlit
Argument: new version string (e.g. 0.0.7).
Steps
1. Confirm version
Read pyproject.toml to get the current version. Tell the user: current → new. Ask for confirmation before proceeding.
2. Gather changes since last release
# Get the previous release tag
PREV=$(gh release list --limit 1 --json tagName --jq '.[0].tagName')
# Fetch that tag locally so git log works
git fetch origin tag "$PREV" --no-tags 2>/dev/null || true
# List commits since then
git log "${PREV}..HEAD" --oneline
Read the commit list and write concise release notes in this format — focus on user-visible changes, group by type, omit chore/internal noise unless significant:
## What's changed
### Features
- ...
### Fixes
- ...
### Docs
- ...
Omit any section that has nothing to list. Keep bullets short (one line each).
3. Bump version
Edit pyproject.toml: replace version = "<old>" with version = "<new>".
4. Commit and push
git add pyproject.toml
git commit -m "chore: bump version to <new>"
git push
5. Publish release
gh release create v<new> \
--title "v<new>" \
--notes "<release notes markdown>"
Return the release URL to the user.