Installs into .claude/skills of the current project.
Are you the author of Release?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ldayton-release)
---
name: release
description: Create a release PR with version bump and changelog
disable-model-invocation: true
argument-hint: [version]
---
Create a PR with branch name `release/v$ARGUMENTS` containing only these changes:
1. Update version in `pyproject.toml` and `src/dippy/__init__.py`
2. Run `uv sync -U` to update dependencies
3. Run `/verify-counts` and update any STALE or FAIL claims
No other changes—no refactors, no fixes, no documentation updates.
## Changelog
Generate release notes from commits since the last tag:
```
git log $(git describe --tags --abbrev=0)..HEAD --oneline
```
Focus on what matters to users:
- New features and capabilities
- Breaking changes or behavior changes
- Group all bug fixes as "Various bug fixes" (don't itemize)
- If Parable was updated, just say "Bump Parable version"
- Omit internal refactors, test changes, and CI updates
Put the changelog in the PR body. The workflow extracts it for the GitHub release.
Run `just check` before pushing. PR title: `Release v$ARGUMENTS`
## After merge
Tag, push, and clean up:
```
git checkout main && git pull && git tag v$ARGUMENTS && git push --tags && git push origin --delete release/v$ARGUMENTS
```
The tag triggers a workflow that creates the GitHub release and updates the Homebrew tap.
