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
npx skills add screenpipe/screenpipe --skill release -a claude-codeWhat 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.tomlto 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-code2Manually: put the files in place
~/.claude/skills/release/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/release/
1Skills CLI (Vercel)
npx skills add screenpipe/screenpipe --skill release -a codex2Manually: put the files in place
.agents/skills/release/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add screenpipe/screenpipe --skill release -a cursor2Manually: put the files in place
.cursor/skills/release/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install screenpipe/screenpipe .claude/skills/release2Manually: put the files in place
.github/skills/release/SKILL.md1Skills CLI (Vercel)
npx skills add screenpipe/screenpipe --skill release -a gemini-cli2Platform CLI
gemini skills install https://github.com/screenpipe/screenpipe --path .claude/skills/releaseManually: put the files in place
.devin/skills/release/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add screenpipe/screenpipe --skill release -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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.