SkillHub ClubShip Full StackFull Stack

release

Create a release PR with version bump and changelog

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars

Hot score

Updated

March 20, 2026

Overall rating

C2.6

Composite score

2.6

Best-practice grade

B84.0

Install command

npx @skill-hub/cli install ldayton-dippy-release

Repository

ldayton/Dippy

Skill path: .claude/skills/release

Create a release PR with version bump and changelog

Open repository

Best for

Primary workflow: Ship Full Stack.

Technical facets: Full Stack.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: ldayton.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

Install release into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
Review https://github.com/ldayton/Dippy before adding release to shared team environments
Use release for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
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.