From codixing
Complete Codixing release pipeline — version bump in 5 locations, tests, docs, CI review, benchmark, blog, X post, tag, publish. Use /codixing-release [version] to ship a new version.
How this skill is triggered — by the user, by Claude, or both
Slash command
/codixing:codixing-releaseThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Ship a new Codixing version from code to announcement. Every step is automated.
Ship a new Codixing version from code to announcement. Every step is automated.
Follow ALL steps. No skipping. No deferring. Every release that skipped steps needed fix PRs.git status # must be clean
git log --oneline -10 # review what's shipping
Run each check SEPARATELY and verify exit code before proceeding:
cargo test --workspace # count total tests from output
cargo clippy --workspace -- -D warnings
cargo fmt --check
If ANY fails, fix first. Do NOT pipe through awk/tail — that masks failures.
Determine version from git log since last tag. Then update ALL of:
Cargo.toml — workspace.package.versionnpm/package.json — "version"docs/install.sh — VERSION=claude-plugin/.claude-plugin/plugin.json — "version".claude-plugin/marketplace.json — metadata.version AND plugins[0].versionVerify: grep -rn "NEW_VERSION" Cargo.toml npm/package.json docs/install.sh claude-plugin/.claude-plugin/plugin.json .claude-plugin/marketplace.json
Update ALL of these. Grep for OLD counts to find strays:
"[0-9]+ MCP tools" and "[0-9]+ tests")# Find any remaining old counts:
grep -rn "OLD_TEST_COUNT\|OLD_TOOL_COUNT" README.md CLAUDE.md docs/index.html
Run from the repo root:
./target/release/codixing init benchmarks/repos/openclaw --no-embeddings --wait
python3 benchmarks/queue_v2_benchmark.py --repo openclaw
Report actual R@10 numbers. Do NOT predict. If OpenClaw not available, say "benchmark TBD."
git checkout -b release/vX.Y.Z
git add -A
git commit -m "release: vX.Y.Z — [summary]
- [bullet points]"
git push -u origin release/vX.Y.Z
gh pr create --title "release: vX.Y.Z — [summary]" --body "..."
gh pr checks N — wait until ALL greengh api repos/ferax564/codixing/pulls/N/comments | python3 -c "import json,sys; [print(f'{c[\"user\"][\"login\"]}: {c[\"body\"][:200]}') for c in json.load(sys.stdin)]"gh pr merge N --squash
git checkout main && git pull
# Auto-tag fires but GITHUB_TOKEN won't trigger release.yml. Re-push:
sleep 15 && git fetch --tags
git tag -d vX.Y.Z 2>/dev/null; git push origin :refs/tags/vX.Y.Z 2>/dev/null
git tag vX.Y.Z && git push origin vX.Y.Z
# Clean up branch:
git branch -d release/vX.Y.Z; git push origin --delete release/vX.Y.Z
# Wait for release workflow:
gh run list --workflow release.yml --limit 1
# When complete:
gh release view vX.Y.Z
Update release notes:
gh release edit vX.Y.Z --notes "$(cat <<'EOF'
## What's New in vX.Y.Z
### [Feature 1]
[Description]
### [Feature 2]
[Description]
### Install
curl -fsSL https://codixing.com/install.sh | bash
npm install -g codixing
**Full Changelog**: https://github.com/ferax564/codixing/compare/vPREV...vX.Y.Z
EOF
)"
Write to docs/blog-*.html. Commit and push to main.
# Check automarketing repo:
ls ~/code/automarketing/social/scripts/post.py
Create ~/code/automarketing/social/approved/YYYY-MM-DD-x-codixing-vXYZ.md:
---
platform: x
type: single
status: approved
created: YYYY-MM-DDTHH:MM:SSZ
tags: [codixing, release, vX.Y.Z, ai-agents, developer-tools, mcp]
---
[post content — casual first person, real numbers, not a press release]
cd ~/code/automarketing
python3 social/scripts/post.py --file social/approved/YYYY-MM-DD-x-codixing-vXYZ.md --dry-run
# Ask user approval, then:
python3 social/scripts/post.py --file social/approved/YYYY-MM-DD-x-codixing-vXYZ.md
npx claudepluginhub ferax564/codixing --plugin codixingAutomates releases for projects using Keep a Changelog and GitHub: bump detection, CHANGELOG promotion, merge to main, tag, and GitHub Release with a single confirmation gate.
Discovers and executes a project's release procedure with preflight checks and step-by-step confirmation. Proposes version bump from CHANGELOG and halts on first failure.
Validates and executes software releases with changelog generation, version bumping, git tagging, and CI verification.