Skip to content
Skills Library
DevOps & cloud · Automation

commit-and-release

/commit-and-release

Commits changes in English without AI co-author trailers, updates CHANGELOG.md, tags a vX.Y.Z release, and pushes to trigger GoReleaser. Use when asked to commit, tag, cut a release, or publish a new version of i-mux.

Repository
i-mux ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Commits changes in English without AI co-author trailers, updates CHANGELOG.md, tags a vX.Y.Z release, and pushes to trigger GoReleaser. Use when asked to commit, tag, cut a release, or publish a new version of i-mux.

Original author description

Commits changes in English without AI co-author trailers, updates CHANGELOG.md, tags a vX.Y.Z release, and pushes to trigger GoReleaser. Use when asked to commit, tag, cut a release, or publish a new version of i-mux.

How it works

  1. Hard rules
  2. Commit format
  3. Pre-commit checks
  4. Release steps
Original SKILL.md headings · 71 lines, 415 words
SKILL.md preview
---
name: commit-and-release
description: Commits changes in English without AI co-author trailers, updates CHANGELOG.md, tags a vX.Y.Z release, and pushes to trigger GoReleaser. Use when asked to commit, tag, cut a release, or publish a new version of i-mux.
---

# Commit and release

## Hard rules

- **English only:** Every commit subject, commit body, tag message, `CHANGELOG.md` entry, `ARCHITECTURE.md` section, and `TASKS.md` item must be written in English.
- **No AI co-authors:** **Never** add `Co-Authored-By:` lines (or any trailer/mention) for Claude, Antigravity, Gemini, Copilot, Codex, OpenCode, or any other AI agent. Commit strictly as the repository's configured Git author.
- **Safe local binary install:** Never run `cp bin/imux ~/.local/bin/imux` or `go build -o ~/.local/bin/imux`. Always use `make install-local` so macOS does not kill running `imux` processes (`SIGKILL: Code Signature Invalid`).

## Commit format

Follow the repository's commit history style:

1. **Docs commit first** (when adding or updating a design/milestone in `ARCHITECTURE.md` and `TASKS.md`):
   ```text
   docs: <Sentence-case summary> (M<N>)
   ```
   Example: `docs: Sidebars come back after imux is killed (M41)`

2. **Code and release commit:**
   ```text
   <type>: <Sentence-case summary under 72 chars>

   <Concise English explanation of why the change was made and what it does,
   wrapped at ~72 columns. No Co-Authored-By trailers.>
   ```
   - Allowed `<type>` prefixes: `feat`, `fix`, `ci`, `docs`, `refactor`, `perf`, `test`, `e2e`.
   - Capitalize the first word after `<type>: ` (e.g., `feat: Project skills in the sidebar`, `fix: Sidebars come back after imux was killed`).

## Pre-commit checks

Run every check CI runs, here, before creating the code commit and again before tagging (the
`check-before-push` skill, `.agents/skills/check-before-push/SKILL.md`):

```sh
make ci
```

It covers Linux and macOS (a symlinked `TMPDIR`), lint, generated files (`docs/CONFIG.md`),
fixtures and e2e. **Do not commit, tag or push while it
fails**, and tell the user which checks could not run on this machine.

## Release steps

1. **Choose the next version (`v0.Y.Z`):**
   - Check the latest tag:
     ```sh
     git tag --sort=-version:refname | head -n 5
     ```
   - Bump minor (`v0.Y.0`) for `feat:` releases; bump patch (`v0.Y.Z`) for `fix:` or `ci:` releases.

2. **Update `CHANGELOG.md` (and `TASKS.md` / `README*.md` if applicable):**
   - Under `## [Unreleased]`, add `## [<0.Y.Z>] - YYYY-MM-DD` (no `v` prefix in the heading, e.g., `## [0.36.2] - 2026-11-09`) with `### Added`, `### Changed`, or `### Fixed` bullets in English.
   - Mark completed tasks `[x]` in `TASKS.md`.

3. **Commit (without `Co-Authored-By`):**
   - Stage only the intended files (`git status`, `git diff --staged`).
   - Commit in English and verify with `git show -s --format=fuller HEAD` that no `Co-Authored-By` trailer is present.

4. **Tag in `v0.Y.Z` format and push:**
   ```sh
   git tag v0.Y.Z
   git push origin main v0.Y.Z
   ```
   Pushing `v0.Y.Z` triggers `.github/workflows/release.yml` (GoReleaser archives, Homebrew tap update, and `release-smoke.yml`).

5. **Update local binary (optional):**
   ```sh
   make install-local
   ```

Versions

The database has no other skills named commit-and-release.

Database snapshot: 13.11.2026 · package version 2a6caef50dfd (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100release
    Cut a new release of ra-mcp. Determines the next version from the commit history since the last tag, bumps pyproject.toml, commits, tags, and pushes. Use when: "make a release", "cut a release", "release", "bump version", "tag a new version", "publish a new version".
  • 100release-ccs
    Publish a new ccfullsearch release. Bumps version, updates CHANGELOG, commits, tags, pushes, and waits for CI + cargo-dist. Use when user says "release", "publish", "new version", or "зарелизь".
  • 100release
    Cut a release of pyhubblenetwork — bumps version, generates release notes from commits, commits, tags, and pushes to trigger the PyPI release workflow. Use this skill when the user wants to release, publish, cut a release, bump version, or push a new version to PyPI. Invoke via /release.
  • 86commit-push-release
    Commit, push, and for "release" run `bun repo release` from the main checkout (it bumps, stamps CHANGELOG.md, pushes, waits on CI, tags), then `bun repo release wait <tag>`. Use for /commit-push-release, "commit push release", "release". Must push. Never force-push. No bun/npm/gh publish.
  • 100release
    Release a new paperus version (0.0.N) - check it is ready, set the versions, write the changelog, tag, and watch the Release workflow publish it. Use when asked to release, publish or tag a version.
  • 100release-sidecar
    Release new versions of sidecar. Covers version tagging with semver, td dependency updates, go.mod validation, CHANGELOG updates, GoReleaser automation, Homebrew tap updates, and verification steps. Use when preparing or executing a release.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.