← ClaudeAtlas

soleri-releaselisted

Triggers: "release", "bump version", "publish packages", "cut a release", "version bump", "npm publish". Bumps monorepo versions, commits, tags, pushes to trigger CI release. Use deliver-and-ship for quality gates.
adrozdenko/soleri · ★ 6 · AI & Automation · score 74
Install: claude install-skill adrozdenko/soleri
# Release — Version Bump & Publish Bump all monorepo package versions in lockstep, commit, tag, and push to trigger the CI/CD release pipeline. This skill handles the mechanical release process — it does NOT run quality gates (use `deliver-and-ship` for that). ## When to Use - After a feature or fix has landed on main and is ready to publish - When the user explicitly asks to bump, release, or publish - NOT for pre-release checks — that is `deliver-and-ship` ## When NOT to Use - Mid-development — features should be merged first - Before tests pass — run `deliver-and-ship` first if unsure - For individual package releases — this bumps ALL packages in lockstep ## Workflow ### Step 1: Vault Check Search the vault for release-related anti-patterns before proceeding. Known issues (like npm publish skip patterns swallowing auth errors) should inform the release. ``` YOUR_AGENT_core op:search_intelligent params: { query: "release publish npm version bump anti-pattern", mode: "scan", limit: 5 } ``` ### Step 2: Determine Current Version Read the root `package.json` to get the current version. Verify all packages are in sync. ```bash grep '"version"' package.json packages/*/package.json ``` If any package version is out of sync, stop and flag it to the user before proceeding. ### Step 3: Determine Bump Type Ask the user if not specified. Follow semver: | Type | When | Example | | ------- | -----------------