autobot-release
Skill47 starsChanged 8 months agoMITView on GitHub
Create proper releases following EVALinux standards with signed tags and changelogs
- Commits and pushes
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/llms.txtllms.txt
- autobot-providerSkill
- autobot-testSkill
- autobot-toolSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Ensure all checks pass before releasing:
- Distinctive: line 25
Follow Semantic Versioning (SemVer):
- Distinctive: line 73
Create release via GitHub CLI:
- Distinctive: line 89
Use this skill when:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Release Workflow
Prerequisites
Ensure all checks pass before releasing:
crystal spec # All tests must pass
./bin/ameba # No warnings or failures
make release # Build must succeedVersion Bump
Follow Semantic Versioning (SemVer):
- MAJOR - Breaking changes (incompatible API changes)
- MINOR - New features (backward compatible)
- PATCH - Bug fixes (backward compatible)
Update version in:
shard.yml(Crystal standard)- Git tag
Git Commands
# 1. Update version in shard.yml
# 2. Commit version bump
git add shard.yml
git commit -m "chore(release): bump version to 1.2.3"
# 3. Create signed tag (requires GPG key)
git tag -s v1.2.3 -m "Release v1.2.3"
# 4. Push with tags
git push origin main --follow-tagsConventional Commits
Use throughout development:
feat:- New featurefix:- Bug fixdocs:- Documentation onlystyle:- Formatting, missing semicolons, etc.refactor:- Code change that neither fixes bug nor adds featureperf:- Performance improvementtest:- Adding testschore:- Build process or auxiliary tool changes
Format:
type(scope): description
[optional body]
[optional footer]GitHub Release
Create release via GitHub CLI:
gh release create v1.2.3 \
--title "Release v1.2.3" \
--verify-tagOr manually:
- Go to GitHub Releases
- Click "Draft a new release"
- Choose the signed tag
- Add release notes
- Publish release
When to Use
Use this skill when:
- Preparing a new release
- Creating version tags
- Bumping version numbers
- Publishing to GitHub
Related Skills: autobot-test
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

