Skip to main content
skill CX Codex

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.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add ldayton/Dippy --skill release -a claude-code
Open on GitHub

What 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.toml and src/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-code

2Manually: put the files in place

~/.claude/skills/release/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/release/

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.

release tobi This skill manages a project release by checking the changelog, installing git hooks, and updating release versions. Use it when the project has a defined release flow. CX Codex +1 2,200installs release Yeachan-Heo A repo-aware skill that discovers release rules from CI files, caches them in .omc/RELEASE_RULE.md, and guides releases. Helpful when preparing tags and version bumps. CX Codex +1 838installs release parcadei Runs a release through five subagents: security audit, E2E tests, final review, version bump, release notes. Useful right before a production deploy. CX Codex +1 481installs release cyrusagents This skill walks a Cyrus CLI release through trusted publishing: prepare, verify, publish, finish. Useful when a version has to ship without touching packages by hand. CX Codex +1 829installs release modelcontextprotocol Walks one milestone release from the release issue through audit, version bumps and the merge PR to the GitHub Release a maintainer publishes. CX Codex +1 ★ 91,595repo stars triage Matt Pocock This skill moves issues and external PRs through triage states, verification, and agent briefs. It fits maintainers managing an issue queue. 990,453installs code-review Matt Pocock Reviews changes from a chosen reference point against repository standards and the originating spec. Use it for a branch, PR, or work in progress. 789,521installs implement Matt Pocock Implements work from a specification or tickets, following a test-driven flow and ending with review and a commit. Use it when a coding task needs a defined delivery routine. 774,700installs git-guardrails-claude-code Matt Pocock This skill adds a Claude Code hook that stops risky Git commands before they run. Use it when an agent must not push or discard working-tree changes. 499,069installs setup-pre-commit Matt Pocock This skill configures pre-commit checks for a JavaScript repository, running Prettier, type checking, and tests before each commit. 489,289installs scaffold-exercises Matt Pocock This skill builds course exercise directories with sections, problems, solutions, and explainers. Use it when starting a new course section or creating exercise stubs. 480,196installs

From the same set5

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor