.claude/skills/release/SKILL.md
# Release Skill Trigger: release, new release, push release, tag release ## Description Creates a new banjo release by tagging HEAD and pushing to GitHub. CI builds cross-platform binaries automatically. ## Steps 1. **Run tests locally** ```bash zig build test ``` 2. **Get current version** ```bash grep 'version = "' src/acp/agent.zig | head -1 ``` Current version: 0.1.0 3. **Delete existing release and tag (if replacing)** ```bash gh release delete v0.1.0 --yes
npx skillsauth add joelreymont/banjo .claude/skills/releaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Trigger: release, new release, push release, tag release
Creates a new banjo release by tagging HEAD and pushing to GitHub. CI builds cross-platform binaries automatically.
Run tests locally
zig build test
Get current version
grep 'version = "' src/acp/agent.zig | head -1
Current version: 0.1.0
Delete existing release and tag (if replacing)
gh release delete v0.1.0 --yes --cleanup-tag 2>/dev/null || true
git push origin :refs/tags/v0.1.0 2>/dev/null || true
git tag -d v0.1.0 2>/dev/null || true
Create and push tag
git tag v0.1.0
git push origin v0.1.0
Monitor CI build
gh run list --workflow=release.yml --limit=1
gh run watch --exit-status
Verify release artifacts
gh release view v0.1.0
Should have:
Update extension.toml with SHA256 hashes
# Download and get hashes from release
gh release download v0.1.0 --pattern '*.sha256' --dir /tmp
cat /tmp/*.sha256
Add sha256 = "..." to each target in extension.toml
src/acp/agent.zig as pub const versiontesting
Check Zed editor logs for banjo/agent errors. Use when user says "check zed logs", "zed errors", or "what's the zed error".
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.