release-checklist
Use this skill before every release; drive the release through a dedicated release/v* branch, verification, changelog review, PR publish, and CI tagging without skipping checks.
- License 许可
- MIT
- 所属仓库
- sazlin/loadout
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- release-checklist
- metadata
- { "loadout.sha": "49eb9bd", "loadout.source": "skills/release-checklist/SKILL.md", "loadout.managed": "true" }
- description
- Use this skill before every release; drive the release through a dedicated release/v* branch, verification, changelog review, PR publish, and CI tagging without skipping checks.
03 SKILL.md 正文
Release checklist
- Confirm the intended semver, release scope, and that work starts from
mainormaster. - Create dedicated branch
release/vX.Y.Zfrom the default branch tip — never land release commits directly on the default branch. - Commit version bumps and CHANGELOG updates on that branch only (
## X.Y.Zsection; bumppyproject.toml,src/loadout/__init__.py, and lockfile as needed). - Review the full diff and user-facing CHANGELOG for that version.
- Run the full required lint, test, build, and packaging checks from a clean state (or via
just release). - Verify version consistency across branch name (
release/vX.Y.Z),CHANGELOG.md(## X.Y.Z),pyproject.toml, andsrc/loadout/__init__.py. - Publish with
just release X.Y.Z(push + open PR) and merge after review — do not create or push git tags locally; CI owns tagging on the merge commit. - After merge, confirm annotated tag
vX.Y.Zexists; record rollback as consumers pinning the previous tag.
04 同仓库更多 Skills
demo
Demo skill
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback