pickfit

BrowseDeveloper CLIs

semrel

Go tool that automates semantic releases by computing SemVer from commits and publishing versions.

Tested on Linux

Use it

Linux x86_64

  1. Download versioned semrel tarball and inspect

    curl -sSL -o /tmp/semrel.tar.gz https://github.com/SemRels/semrel/releases/download/v0.28.3/semrel_0.28.3_linux_amd64.tar.gz && mkdir -p ~/.local/bin
  2. Install semrel binary to local bin

    mkdir -p /tmp/sx2 && tar -xzf /tmp/semrel.tar.gz -C /tmp/sx2 && cp /tmp/sx2/semrel ~/.local/bin/semrel && chmod +x ~/.local/bin/semrel && semrel --version
Where the README and reality differ
  • README: curl -sSL https://github.com/SemRels/semrel/releases/latest/download/semrel_linux_amd64.tar.gz | tar -xz semrel + sudo mv
    What worked: download versioned asset https://github.com/SemRels/semrel/releases/download/v0.28.3/semrel_0.28.3_linux_amd64.tar.gz (assets are per-version), extract in an empty dir and copy semrel to ~/.local/bin (no sudo)
  • README: semrel release --dry-run with zero side effects after semrel config init
    What worked: replace default plugins with minimal core-only .semrel.yaml (plugins: []) before offline dry-run; default config auto-installs condition-github-actions and fails its condition check outside GitHub Actions

Check that it works

semrel --version

The output should contain “semrel version v0.28.3+dirty”.

First thing to try

rm -rf /tmp/demorepo && mkdir -p /tmp/demorepo && cd /tmp/demorepo && git init -q && git config user.email "test@example.com" && git config user.name "Test" && echo "# demo" > README.md && git add README.md && GIT_AUTHOR_DATE="2024-01-01T00:00:00Z" GIT_COMMITTER_DATE="2024-01-01T00:00:00Z" git commit -qm "feat: initial feature" && echo "change" >> README.md && git add README.md && GIT_AUTHOR_DATE="2024-01-02T00:00:00Z" GIT_COMMITTER_DATE="2024-01-02T00:00:00Z" git commit -qm "fix: a bug fix" && semrel config init && cat .semrel.yaml
cd /tmp/demorepo && git branch -M main && semrel doctor

Inside a Git repository, run semrel doctor to check your setup, then semrel config init to create a .semrel.yaml config file.

What it does

  • Work out the next SemVer version from commits
    How to use it
    1. In your Git repository, run semrel config init to create .semrel.yaml, and set your branch and bump rules (for example feat to minor, fix to patch).
    2. Run semrel release --dry-run to see the next version without releasing.
    Tested
  • Generate Keep-a-Changelog release notes
    How to use it
    1. In a repository with a .semrel.yaml config, run semrel changelog.
    Tested
  • Update version manifests across language ecosystems
    Not tested
  • Create releases on Git forges
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 2 of 4 features work
  4. Works offline

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • compute next SemVer version from Conventional Commits
  • generate Keep-a-Changelog release notes
  • validate commits against Conventional Commits

An alternative to semantic-release, GoReleaser, release-please, release-it and changesets.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version v0.28.3+dirty

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.