releasing-software — Claude Code skill: releases and setup
This skill walks through release checks, from builds and tests to CI and tagging. Use it to hold off on a tag until CI succeeds.
npx skills add harperreed/dotfiles --skill releasing-software -a claude-codeWhat releasing-software does
Before a release, the skill checks build paths in goreleaser.yml, GitHub Actions workflows, the Makefile, and Dockerfile. Its checklist also covers Go test files, local tests and builds, documentation, release settings, and Git status. It asks the agent to create a TodoWrite item for each checklist entry.
Once checks pass, the sequence is to commit changes, let pre-commit hooks finish, push the branch, and wait for green CI before creating and pushing a tag. Afterward, the skill checks the release workflow and its assets. In Go 1.23+, a coverage step can fail when a package has no test file, so inspect packages before running CI. The guide also explains patch, minor, and major version bumps.
What it helps with
- check build paths before a release
- find Go packages without test files
- compare local checks with CI
- update version references and release docs
- verify the release workflow after pushing a tag
Example prompts for the agent
- Prepare a release: check builds, tests, docs, and Git status.
- Review the project before tagging, and wait for CI to pass.
- Find Go packages without tests and check the coverage step.
How to install releasing-software
1Skills CLI (Vercel)
npx skills add harperreed/dotfiles --skill releasing-software -a claude-code2Manually: put the files in place
~/.claude/skills/releasing-software/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/releasing-software/
1Skills CLI (Vercel)
npx skills add harperreed/dotfiles --skill releasing-software -a codex2Manually: put the files in place
.agents/skills/releasing-software/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add harperreed/dotfiles --skill releasing-software -a cursor2Manually: put the files in place
.cursor/skills/releasing-software/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install harperreed/dotfiles releasing-software2Manually: put the files in place
.github/skills/releasing-software/SKILL.md1Skills CLI (Vercel)
npx skills add harperreed/dotfiles --skill releasing-software -a gemini-cli2Platform CLI
gemini skills install https://github.com/harperreed/dotfiles --path .claude/skills/releasing-softwareManually: put the files in place
.devin/skills/releasing-software/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add harperreed/dotfiles --skill releasing-software -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about releasing-software
How do I install releasing-software in Claude Code?
Run npx skills add harperreed/dotfiles --skill releasing-software -a claude-code. The skill file is at ~/.claude/skills/releasing-software/SKILL.md.
What does releasing-software do?
It guides pre-release checks and puts successful CI before tag creation. After the tag is pushed, it prompts you to inspect the release workflow and assets.
Why check Go packages before running coverage?
The guide notes that coverage in Go 1.23+ can fail when a package has no test file. The skill includes a check for test files before CI runs.