mistakenot/release
skills/release/SKILL.md
Create a new auto-stack release by tagging a commit and pushing the tag. The GitHub Actions release workflow builds binaries and publishes the release.
development
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add mistakenot/auto-stack releaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 9:00 PM55.2s1 file scanned
SKILL.md
- name:
- release
- description:
- >-
- license:
- MIT
Release
Create a new auto-stack release. The agent's only job is to tag and push — GitHub Actions handles building and publishing.
How It Works
- You push a semver tag (e.g.
v0.8.0) to the repo. - The
.github/workflows/release.ymlworkflow triggers onv*tags. - It cross-compiles all binaries for
linux-amd64anddarwin-arm64. - It creates (or updates) a GitHub Release with the binaries attached.
- Users install via
curl -fsSL https://raw.githubusercontent.com/mistakenot/auto-stack/main/install.sh | bash.
Steps
Step 1: Determine the next version
# Get the latest release tag
LATEST=$(git tag --sort=-v:refname | head -1)
echo "Latest tag: $LATEST"
Check what has changed since the last release:
git log ${LATEST}..HEAD --oneline
Apply semver:
- Patch (v0.7.0 -> v0.7.1): bug fixes only
- Minor (v0.7.0 -> v0.8.0): new features, non-breaking changes
- Major (v0.7.0 -> v1.0.0): breaking changes
Ask the user to confirm the version before proceeding.
Step 2: Verify the build
Run the full build and tests to make sure everything compiles:
make build
make test
Do not proceed if either fails.
Step 3: Tag and push
VERSION="v0.8.0" # use the confirmed version
git tag "$VERSION"
git push origin "$VERSION"
Step 4: Monitor the release
Check that the workflow succeeded:
# Wait a moment for the workflow to start, then check
gh run list --workflow=release.yml --limit=1
If the run fails, check logs with:
gh run view <run-id> --log-failed
Step 5: Verify the release assets
gh release view "$VERSION" --json assets --jq '.assets[].name'
Expected assets for each binary (autodoc, autoetl, autosearch, autowatch, autoskill):
<binary>-linux-amd64<binary>-darwin-arm64
Important
- Do not create releases through the GitHub UI. Always push tags from the CLI. The workflow creates the release.
- Do not force-push or move tags. If a release fails, diagnose and fix the issue, then create a new patch version.
- All binaries must compile before tagging. The CI build will fail if any sub-project has errors.
Related Skills
mistakenot/readme-updater
tools
VerifiedTrustedCommunity
Bring a project's README up to date with the current state of the codebase. Audits the existing README for stale commands, dead links, renamed tools, and drifted status claims; surveys what's changed since the README was last touched; rewrites it with verified facts; then commits and pushes. Use this skill whenever the user says "update the README", "the readme is stale", "refresh the README", "rewrite README.md", "add new features to the readme", or otherwise asks for documentation that reflects the current state of the project. Also trigger when a README clearly hasn't kept pace with the codebase (e.g. recent feature commits not reflected, broken examples).
SKILL.mdUpdated Jun 4, 2026
mistakenot/self-improve
tools
VerifiedTrustedCommunity
Run the self-improvement loop on a focus area. Use when the user asks to improve, fix recurring problems, or run self-improve on a tool. Trigger when: "self-improve", "improve autosearch", "find and fix problems in". Do not trigger for doc reviews or one-off bug fixes.
SKILL.mdUpdated Apr 25, 2026
mistakenot/recall
development
VerifiedTrustedCommunity
Reconstruct and narrate the current development context from contextual commits. Run at session start, when resuming work, or when switching branches. Produces a brief, conversational summary of where things stand.
SKILL.mdUpdated Apr 25, 2026
mistakenot/new-package
tools
VerifiedTrustedCommunity
Scaffold a new auto-* package in the auto-stack monorepo. Creates the full directory structure, Go source files, go.mod, CLAUDE.md, and Makefile integration following established patterns. Use when: "create a new package", "add auto-foo", "scaffold a new tool", "new auto package".
SKILL.mdUpdated Apr 25, 2026