release · ldayton — Claude Code skill: what it does, how to install
Prepares a release pull request with version bumps, dependency sync, and user-facing release notes. Helpful for structured project publishing.
npx skills add ldayton/Dippy --skill release -a claude-codeWhat release does
This skill prepares a release pull request inside a dedicated release/v<version> branch. It strictly limits modifications to updating version values in pyproject.toml and src/dippy/__init__.py, running uv sync -U to refresh dependencies, and running /verify-counts. Code refactors or unrelated bug fixes are explicitly avoided.
The changelog pulls commit messages since the previous tag via git log. It focuses on features and breaking changes, grouping generic bug fixes together. The process requires passing just check before pushing the branch.
This workflow targets the Dippy repository layout and expects uv alongside just in your environment.
What it helps with
- bump version numbers across
pyproject.tomlandsrc/dippy/__init__.py - compile user-focused changelogs from git commit history
- synchronize package dependencies using
uv sync -U - generate a clean release pull request without accidental changes
Example prompts for the agent
- /release 0.4.0
- Create a release PR for version 1.2.0
- /release 1.0.1
How to install release
1Skills CLI (Vercel)
npx skills add ldayton/Dippy --skill release -a claude-code2Manually: put the files in place
~/.claude/skills/release/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/release/
1Skills CLI (Vercel)
npx skills add ldayton/Dippy --skill release -a codex2Manually: put the files in place
.agents/skills/release/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ldayton/Dippy --skill release -a cursor2Manually: put the files in place
.cursor/skills/release/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ldayton/Dippy release2Manually: put the files in place
.github/skills/release/SKILL.md1Skills CLI (Vercel)
npx skills add ldayton/Dippy --skill release -a gemini-cli2Platform CLI
gemini skills install https://github.com/ldayton/Dippy --path .claude/skills/releaseManually: put the files in place
.devin/skills/release/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ldayton/Dippy --skill release -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about release
How to install release in Claude Code?
Run npx skills add ldayton/Dippy --skill release -a claude-code. Alternatively, save the file to ~/.claude/skills/release/SKILL.md.
What does the release skill do?
It creates a release branch, bumps version strings, updates dependencies with uv, and compiles release notes directly into the pull request description.
What tools does release require?
The workflow relies on git, uv, and the just task runner. It also expects the repository to support /verify-counts.
Source text
SKILL.md · MIT
--- 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.
© ldayton · MIT · ldayton/Dippy
Similar skills
All skills for Git and GitHub →release by other authors comes first.