// Use when cutting a release — composing the `## [vX.Y.Z]` `CHANGELOG.md` section, picking the version bump, and walking commits since the last tag. Authoring only; the maintainer pushes the tag (which triggers GoReleaser + provenance signing) and the deploy bot auto-bumps Helm `values.yaml`.
Use when picking a branch name, staging files, or writing a commit message — covers branch conventions, the project's Conventional Commits format with the scope vocabulary observed in history, and the documentation-update gate that fires before every commit (`docs/*`, `README.md`, godoc, Helm values).
Use when opening or updating a pull request, responding to review, or filing a GitHub issue — covers the PR body skeleton matched to recent merged PRs, draft → ready → squash mechanics, rebase-vs-merge policy, and the issue-template routing (`bug_report.yml` / `feature_request.yml`, blank issues disabled).
Use when deciding whether to run an out-of-process test suite (real binary or live instance) — picks between `make smoke`, `make abs-contract`, and `make predeploy-smoke` after the unit suite passes but you've changed handler wiring, scheduler jobs, downloader integration, ABS imports, or anything that boots the binary. For the routine pre-PR matrix (lint / vet / test / typecheck / build) see the `testing` skill.
Use when writing or running Bindery tests, before pushing, or before opening a PR — covers the full pre-PR matrix (lint, vet, govulncheck, test, frontend), pinned tool versions, the project's test patterns (db.OpenMemory, httptest, vitest), and common failure modes.
| name | tag-release |
| description | Use when cutting a release — composing the `## [vX.Y.Z]` `CHANGELOG.md` section, picking the version bump, and walking commits since the last tag. Authoring only; the maintainer pushes the tag (which triggers GoReleaser + provenance signing) and the deploy bot auto-bumps Helm `values.yaml`. |
This skill drafts release artifacts. It does not run git tag, git push --tags, or any deploy. The maintainer pushes tags; the deploy bot owns chore(deploy): promote bindery to vX.Y.Z [skip ci].
SemVer per the CHANGELOG header reference:
| Change shape | Bump |
|---|---|
| Backwards-incompatible API/config (env var renamed, removed feature, breaking schema migration) | major |
| New feature, new env var, new endpoint | minor |
| Bug fixes, doc-only updates, security backports | patch |
From the previous tag to HEAD:
PREV=$(git describe --tags --abbrev=0)
git log --oneline --no-merges "$PREV"..HEAD
git log "$PREV"..HEAD -- CHANGELOG.md docs/ README.md # changes already documented
Group commits by Conventional Commits type → CHANGELOG sub-heading:
| Commit type | CHANGELOG section |
|---|---|
feat | Added |
perf, behaviour-changing chore | Changed |
fix | Fixed |
docs (user-facing only) | Docs |
| Removals / deprecations | Removed |
Skip release-internal commits (chore(release), chore(deploy), [skip ci] from bots).
Read the most recent two ## [vX.Y.Z] sections in CHANGELOG.md before drafting:
CHANGELOG.md v1.4.0–v1.4.3 are the model.(#NN)) and closes #NN when applicable.YYYY-MM-DD, line below the heading.$PREV is represented (or deliberately skipped — internal-only refactors).docs/upgrade-v2.md extended if any breaking-change behaviour shipped.git tag or git push --tags. The maintainer does this.charts/bindery/values.yaml image digest — auto-bumped by the deploy bot per [skip ci] commits.commits skill explicitly defers CHANGELOG to this skill.