Release
Release the screenpipe monorepo. Bumps versions, triggers GitHub Actions for app, CLI, MCP, and JS packages.
Install
npx skills add screenpipe/screenpipe --skill releasegit clone --depth 1 https://github.com/screenpipe/screenpipe.git /tmp/screenpipe
mkdir -p ~/.claude/skills
cp -r /tmp/screenpipe/.claude/skills/release ~/.claude/skills/releasePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Screenpipe Monorepo Release Skill Automate releasing all components of the screenpipe monorepo. ## Components & Versions | Component | Version File | Current Pattern | Workflow | |-----------|--------------|-----------------|----------| | Desktop App | `apps/screenpipe-app-tauri/src-tauri/Cargo.toml` | `version = "X.Y.Z"` | `release-app.yml` | | CLI/Server | `Cargo.toml` (workspace.package) | `version = "0.2.X"` | `release-cli.yml` | | MCP | `packages/screenpipe-mcp/package.json` **and** `server.json` (2 fields) | `"version": "X.Y.Z"` | `release-mcp.yml` | > **MCP has no commit-prefix trigger** — unlike the app, `release-mcp.yml` fires > only on an `mcp-v*` tag or `workflow_dispatch`, and it refuses to run when > `package.json`'s version is already on npm (npm cannot overwrite a published > version, so the run would publish nothing). Follow > `packages/screenpipe-mcp/RELEASE.md` — it has the exact commands and the > post-publish checks. ## When to Release What **Always release CLI** when there are changes under `crates/`. Every shipped Rust crate lives there, and the `screenpipe` CLI binary is built from `crates/screenpipe-engine` (`[[bin]] name = "screenpipe"`), so it links whatever its dependency graph pulls in. That includes `screenpipe-a11y` and `screenpipe-semantic`, which are easy to overlook because they are not named "core" or "server". **App-only release** is fine when changes are only in: - `apps/screenpipe-app-tauri/` (UI/frontend changes)
Details
- Skill name
release- Repository
- screenpipe/screenpipe
- Path
.claude/skills/release/SKILL.md- Repo updated
- 17 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Release skill do?
Release the screenpipe monorepo. Bumps versions, triggers GitHub Actions for app, CLI, MCP, and JS packages.
How do I install the Release skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add screenpipe/screenpipe --skill release. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Release popular?
It lives in screenpipe/screenpipe, which has 22,429 GitHub stars and 2,305 forks, and is included in 1 curated skill list.
Related skills
Develop Screenpipe Windows
22kscreenpipe/screenpipe
Develop and test Screenpipe Windows-native changes on a disposable Azure VM created from the prepared Screenpipe Windows dev image. Use for Windows compiler, process, service, local API, desktop, capture, installer, or permission behavior. Do not use for React-only work proved by the browser mock.
Render HTML Report
22kscreenpipe/screenpipe
Produce a human-facing visual report — a chart, dashboard, scorecard, or styled summary — that renders as a live page in the screenpipe viewer instead of plain text. Use when the task asks for a visual/graphical output rather than a plain note; do NOT use for plain text or raw data (prefer a markdown note for those).
Screenpipe API
22kscreenpipe/screenpipe
Query the user's local and synced-device Screenpipe data via the REST API at localhost:3030. Use for screen activity, meetings, apps, productivity, other-device or cross-device history, media export, retranscription, or connected services.
Plannotator Review
13kbacknotprop/plannotator
Open Plannotator's browser-based code review UI and address the returned feedback.
Repo Guidance
31kComposioHQ/composio
Navigate the Composio SDK monorepo, branch and PR workflow, repo layout, generated-file boundaries, changesets, and shared maintenance rules. Use when work spans multiple packages, when deciding where code belongs, when preparing a PR, or when the user asks about repository conventions rather than a specific SDK implementation.
Plannotator Review
13kbacknotprop/plannotator
Open Plannotator's browser-based code review UI for the current worktree, another directory, or a pull request URL, then act on the feedback that comes back.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.