commits-and-releases
Use when writing commit messages or splitting work into commits; when cutting, versioning, or tagging a release; when editing a CHANGELOG or bumping a version number; when setting up or fixing release-please, semantic-release, or changesets; or when a release has the wrong version or is missing changelog entries.
- License 许可
- MIT
- 所属仓库
- rahulmutt/devkit
- 最近更新
- 2026-10-19
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- commits-and-releases
- description
- Use when writing commit messages or splitting work into commits; when cutting, versioning, or tagging a release; when editing a CHANGELOG or bumping a version number; when setting up or fixing release-please, semantic-release, or changesets; or when a release has the wrong version or is missing changelog entries.
02 资源文件 1
- 参考文档references/release-please.md4.0 KB
03 SKILL.md 正文
Commits and Releases
Commit history is the input to the release: release tooling reads each commit subject to pick the version bump and write the changelog. So a wrong release is fixed by changing that input, never the output.
Commit format, breaking-change syntax, type-to-bump mapping, when to ship, and
fixing merged history: see
references/release-please.md.
Releases come from history, not hand edits
Never hand-edit the changelog, bump version strings or the manifest, or create tags that the release automation owns. That includes the files on the open release PR's branch: the next run regenerates them and your edit is lost or contradicts history.
Fix a wrong release by changing what the tool reads:
- Wrong version: add a commit on the default branch with a
Release-As: X.Y.Zfooter (an empty commit is fine). - Mistyped commit, squash-merged PR: edit the merged PR's body to add a
commit override (
BEGIN_COMMIT_OVERRIDE/END_COMMIT_OVERRIDEaround the corrected message). The squash commit maps to that one PR, so the override applies. - Mistyped commit, plain merge commits: the override is ignored, because
release-please can't tell which of the PR's commits it replaces. Add a new
commit on the default branch whose subject carries the correct type, e.g.
git commit --allow-empty -m "feat: add --json output flag". Don't rely on the override here.
Check which merge strategy the repo uses before choosing between the last two.
Counter-pull: bootstrap steps (the baseline tag, the first 1.0.0) are
deliberately manual.
Boundaries with sibling skills
- Release workflow YAML: pinning, token permissions, runners →
ci-pipelines. - Exposing the gate as a named task →
navigable-codebases. - What the code inside a commit looks like →
writing-clean-code. - Out of scope: PR size and stacking, review etiquette, deploys.
04 同仓库更多 Skills
writing-clean-code
Use when refactoring or restructuring code, splitting a file or module that has grown too large, deciding whether to extract a helper or inline it, naming things, removing dead or unused code, drawing module or package boundaries, handling errors, writing comments, applying DDD or hexagonal (ports and adapters) architecture, or checking a language's idiomatic style.
using-devkit
Use when starting any conversation or new engineering task in a repo with devkit installed — establishes that devkit skills exist and must be checked before acting.
testing-practices
Use when writing, adding, or reviewing tests; choosing between unit, integration, snapshot/golden, property, fuzz, mutation, e2e/UI, or formal methods; when a test is flaky or the suite or CI is slow; or when deciding what runs in pre-commit, PR CI, or nightly.
security-practices
Use when code touches a trust boundary — HTTP endpoints, webhooks, file uploads, auth, sessions, permissions, SQL or shell built from input, deserialization, service-to-service calls — when handling secrets, API keys, or .env files, on a CVE or vulnerability alert, when writing a threat model, or when choosing secret, SCA, SAST, or container scanners.
navigable-codebases
Use when writing or updating a README, AGENTS.md, CLAUDE.md, GEMINI.md, ARCHITECTURE.md, or onboarding docs; when setting up a new repository; when adding or naming task-runner commands (mise tasks, Makefile, justfile, npm scripts); or when getting-started steps are missing, stale, or slow for newcomers.
developer-environment
Use when installing or upgrading any tool, runtime, CLI, or library — brew, apt, npm i -g, pip install, cargo install, nvm, pyenv, asdf — editing mise.toml or .tool-versions, bumping or pinning versions, adding a dependency, hitting "command not found", setting up a dev or CI toolchain, reviewing Renovate or Dependabot version bumps, or considering Bazel.