release

Featured

Coordinate a full Paperclip release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up. Use when leadership asks to ship a release, not merely to discuss versioning.

AI & Automation 114,742 stars 19046 forks Updated today MIT

Install

View on GitHub

Quality Score: 92/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Release Coordination Skill Run the full Paperclip maintainer release workflow, not just an npm publish. This skill coordinates: - stable changelog drafting via `release-changelog` - canary verification and publish status from `master` - Docker smoke testing via `scripts/docker-onboard-smoke.sh` - manual stable promotion from a chosen source ref - GitHub Release creation - website / announcement follow-up tasks - release-content Cases dogfood: a top-level `release` case with child `blog_post` and `tweet_storm` cases, all linked to the release issue/run ## Trigger Use this skill when leadership asks for: - "do a release" - "ship the release" - "promote this canary to stable" - "cut the stable release" ## Preconditions Before proceeding, verify all of the following: 1. `.agents/skills/release-changelog/SKILL.md` exists and is usable. 2. The repo working tree is clean, including untracked files. 3. There is at least one canary or candidate commit since the last stable tag. 4. The candidate SHA has passed the verification gate or is about to. 5. If manifests changed, the CI-owned `pnpm-lock.yaml` refresh is already merged on `master`. 6. npm publish rights are available through GitHub trusted publishing, or through local npm auth for emergency/manual use. 7. If running through Paperclip, you have issue context for status updates and follow-up task creation. If any precondition fails, stop and report the blocker. ## Inputs Collect these inputs up front: - whether t...

Details

Author
paperclipai
Repository
paperclipai/paperclip
Created
8 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

DevOps & Infrastructure Listed

release

Runs a repository's full release process end to end, driven by a `.claude/release.yml` committed to that repo — no hardcoded repo, workflow, or branch names. `/release init` interviews you, writes that config, and opens a PR for it. `/release dry-run` rehearses a release read-only, changing nothing. A full run baselines from the last successful release, reviews every PR merged since, audits docs and screenshots and stops with an [ON HOLD] issue if anything is stale (it reports staleness, never fixes it), opens a labelled review issue for explicit human approval, confirms the ref, deploys the docs site first, dispatches the release workflow with the approved issue's number, tracks it, locates the resulting PR or GitHub Release, announces it, and writes a self-contained HTML record of what shipped. Use on /release, or any ask to cut, ship, publish, or promote a release. Not for feature work (/code-development) or a red pipeline (/ci-pipeline). Needs `gh` or a GitHub MCP server — Claude Code only.

0 Updated 2 months ago
dawg-io
AI & Automation Listed

release

Automated release management - version updates, changelog generation, git tagging, and GitHub release creation

4 Updated today
Edmonds-Commerce-Limited
Code & Development Listed

release

Create a software release by reviewing commits, determining the semantic version, updating the changelog and package versions, committing release metadata, and tagging the result. Use this skill whenever the user asks to cut, prepare, publish, or tag a release.

2 Updated 1 months ago
mohammadhprp