Skip to main content
skill CX Codex

release · screenpipe — Claude Code skill: screenpipe monorepo versioning and deployment

release automates deployment of all screenpipe components: desktop app, CLI, MCP server. Updates versions across files, triggers GitHub Actions, and verifies that dependencies stay in sync.

LicenseRef-Proprietary ★ 22,500 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add screenpipe/screenpipe --skill release -a claude-code
Open on GitHub

What release does

The skill manages three independent releases within a single monorepo. Each component has its own version file: Desktop App in apps/screenpipe-app-tauri/src-tauri/Cargo.toml, CLI in the root Cargo.toml (under [workspace.package]), and MCP in packages/screenpipe-mcp/package.json plus server.json. When you change a version, the skill runs ./scripts/regenerate-locks.sh to recompute all tracked Cargo.lock files—this is mandatory because stale locks break cargo test --locked in CI.

Before releasing the app, the skill checks whether crates/ has changed since the last CLI release. If only the UI changed, that check can pass, but it first verifies the path exists in the repo rather than relying on an outdated location. MCP follows a different pattern: release triggers only on manual workflow_dispatch or an mcp-v* tag, and npm refuses to republish an already-published version, so the skill validates this before dispatch.

Once the version commit lands on main, the skill sends its SHA to GitHub Actions with needs_testing and force_github_runners flags. The workflow builds, signs, and uploads artifacts, but does not publish: that remains a manual step via the website admin panel. Before dispatch, the skill confirms the remote main SHA matches your local commit, and after the build starts, verifies that the running workflow is pinned to exactly the commit you pushed.

What it helps with

  • synchronize versions across three components and send them to GitHub Actions
  • recompute all Cargo.lock files to prevent CI breakage
  • determine whether engine code changed since the last CLI release before shipping an app-only build
  • verify MCP version is not already published on npm
  • dispatch the build with the exact commit SHA and confirm it reaches artifact signing

Example prompts for the agent

  • Show current versions for app, CLI, and MCP and tell me which one to change
  • Update app version in apps/screenpipe-app-tauri/src-tauri/Cargo.toml to 0.4.30, regenerate all Cargo.lock files, and dispatch the release
  • Check whether code under crates/ changed since the last CLI release and decide if a build is needed

How to install release

1Skills CLI (Vercel)

npx skills add screenpipe/screenpipe --skill release -a claude-code

2Manually: put the files in place

~/.claude/skills/release/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/release/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about release

How do I install release in Claude Code?

Run npx skills add screenpipe/screenpipe --skill release -a claude-code in your terminal, then open ~/.claude/skills/release/SKILL.md.

What does the release skill do?

It releases screenpipe components by updating version strings in source files, regenerating all Cargo.lock files, committing to GitHub, and dispatching GitHub Actions to build and sign artifacts.

When should I release only the app without the CLI?

When changes are confined to apps/screenpipe-app-tauri/ (UI only). The skill checks that crates/ has not changed since the last CLI release and validates that the path exists in the repo to avoid missing code that moved.

Similar skills

All skills for DevOps and infrastructure →

release by other authors comes first.

release tobi A skill for Claude Code, Codex, Cursor and other IDE agents that manages project releases: validates CHANGELOG.md, updates dependencies, installs git hooks and cuts releases on command. Runs with /release 1.0.5 or /release patch. CX Codex +1 2,200installs release Yeachan-Heo A repo-aware skill that discovers release rules from CI files, caches them in .omc/RELEASE_RULE.md, and guides releases. Helpful when preparing tags and version bumps. CX Codex +1 904installs Release schpet Release is a Claude Code skill that reviews changes, updates the changelog, and publishes a version. It activates for requests to prepare or create a release. CX Codex +1 3,900installs release different-ai Cuts an OpenWork release from a git tag through GitHub Actions, with no commits to the repo. Checks open fix PRs before tagging and covers reruns after a failure. CX Codex +1 122installs release toss Automates project releases by verifying git status, bumping versions in package files, generating changelog entries, and tagging commits. CX Codex +1 208installs release-bump mikeyobrien release-bump walks ralph-orchestrator through a release: raise the version, build, test, tag. Meant for the moment fixes are committed and publishing is next. CX Codex +1 ★ 3,206repo stars jackin-release-check jackin-project jackin-release-check runs the jackin❯ release-readiness gates and reports a verdict for each one. Use it before cutting a release. CX Codex +1 469installs auto-release-manager Dev-GOM auto-release-manager bumps the version in your project files, builds a CHANGELOG from commits and carries the release through tag and push. Handy when the same release ritual repeats in every repo. CX Codex +1 3installs re0-release LilMGenius re0-release is a Claude Code skill that takes repository changes through the project’s release procedure and publishes a tag after approval. A person starts it when the decision to ship has been made. CX Codex +1 1,400installs release-manager borghei release-manager — a skill for Claude Code, Codex, Cursor, Copilot and Gemini CLI that turns git log output or a JSON plan into a changelog, a SemVer bump and a release readiness score. Run it before every release or hotfix. CX Codex +1 132installs monorepo-manager rohitg00 monorepo-manager — a Claude Code plugin that detects affected packages in a monorepo and synchronizes their versions. The agent sees which parts of the project changed and updates dependencies automatically. ★ 2,858repo stars

From the same set2

Project sponsors

Companies that keep this analytics open