release
Ship a finished milestone safely - readiness gate, version and CHANGELOG, commit, push or pull request, deploy, verify and a rollback plan. Use when asked to release, ship, deploy, publish or tag a version.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- release
- description
- Ship a finished milestone safely - readiness gate, version and CHANGELOG, commit, push or pull request, deploy, verify and a rollback plan. Use when asked to release, ship, deploy, publish or tag a version.
03 SKILL.md 正文
Release
Stop at the first red step and say what is wrong. Pushing, publishing and deploying are seen by other people: before each one, say what it will do and how to undo it, and let the user approve it.
1. Gate
- The milestone's Done when list is met: check each line against the code or by running it.
git statusis clean, or every change belongs to this release.- Install, tests, typecheck and lint pass locally (the commands in CLAUDE.md).
- CI is green on the branch:
gh run list --branch <branch> --limit 5.
2. Prepare
- Version: bump it where the project keeps it (
package.json,pyproject.toml,Cargo.toml, …) following semver: breaking change = major, feature = minor, fix = patch. Skip if the project does not version. - CHANGELOG: add an entry at the top in the project's existing style, written for users: what they can now do, what was fixed, anything they must change.
- Docs and README still describe what ships;
_project/STATUS.mdsays what was released.
3. Ship
- Commit with the project's message style (for example
chore(release): 1.2.0). - Push the branch, or open a pull request with
gh pr createwhen the project merges through pull requests. Never force-push to main or master. - Tag the release when the project tags (
git tag v1.2.0, push the tag), and create the GitHub release from the CHANGELOG entry (gh release create). - Deploy with the project's own command or workflow; do not invent a new deploy path.
4. Verify
- Watch the workflow run to the end (
gh run watchorgh run view). - Check the deployed thing answers: open the URL, run the installed command, or read the package page. Report the links.
5. Rollback plan
Write down, before or right after shipping: the last good version or commit, the command to
roll back (revert and redeploy, or redeploy the previous tag), and how to check it worked.
If the project has no docs/runbook.md, offer to write one with deploy, rollback and health
checks.
04 同仓库更多 Skills
verification-loop
Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS/FAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or when quality gates must pass.
e2e-testing
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI.
browser-qa
Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.
ai-regression-testing
Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code. Use when adding regression coverage to AI-assisted code, or when the same model both wrote and reviewed a change.
story-lifecycle
Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira/Linear/Taiga but needs structured delivery tracking.
intent-driven-development
Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security/data/migration/integration change, prepare implementation requirements for another agent, or make a complex request testable. Do not trigger for trivial edits, straightforward fixes, active debugging, code review, or implementation requests whose acceptance conditions are already clear unless the user explicitly invokes this skill.