Skip to main content
skill CX Codex

release-safety — Claude Code skill for safer releases

The release-safety skill sets release rules for a monorepo: the agent must get explicit permission before skipping checks or tests, and fix failures before retrying.

MIT ★ 14,319 updated 2026-10-23

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

What release-safety does

release-safety applies to monorepo releases, package publishing, and canary releases. Before adding --skip-checks or --skip-tests, the agent must ask for permission. If a check or test fails, it should fix the underlying problem and run the release again.

The skill separates safe flags (--canary, --ci, --dirty, --build-fast) from flags that need explicit approval: --skip-checks, --skip-tests, and --skip-build. One detail matters: skipping the package build also requires permission, even though the main warning focuses on checks and tests.

What it helps with

  • prevent release checks from being skipped without approval
  • fix the cause of a failed release step
  • publish a canary version with --canary
  • identify flags that skip checks, tests, or builds

Example prompts for the agent

  • Prepare yarn release; do not skip checks unless I approve it.
  • Publish a canary release and fix any check failures before retrying.
  • Use --skip-tests only if I explicitly authorize it.

How to install release-safety

1Skills CLI (Vercel)

npx skills add tamagui/tamagui --skill release-safety -a claude-code

2Manually: put the files in place

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

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

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

Questions about release-safety

How do I install release-safety in Claude Code?

Run npx skills add tamagui/tamagui --skill release-safety -a claude-code. The skill file is at ~/.claude/skills/release-safety/SKILL.md.

What does release-safety do?

It gives the agent rules for releases: fix failing checks or tests instead of bypassing them. Skipping them requires explicit permission.

Which flags need explicit permission?

--skip-checks, --skip-tests, and --skip-build all require approval. The rules list --canary, --ci, --dirty, and --build-fast as safe flags.

Source text

SKILL.md · MIT
---
name: release-safety
description: Release safety rules. INVOKE WHEN: yarn release, npm publish, release canary, release packages, publishing, skip checks, skip tests. NEVER skip checks or tests without explicit permission.
---

# release safety

rules for running releases in this monorepo.

## rules

- NEVER add `--skip-checks` unless user explicitly says "skip checks"
- NEVER add `--skip-tests` unless user explicitly says "skip tests"
- if checks or tests fail, FIX THE ISSUES instead of skipping
- ask user before adding any skip flags
- the point of checks is to catch problems before publishing

## when things fail

1. read the error output carefully
2. fix the underlying issue
3. re-run the release
4. do NOT just skip the failing step

## common flags

safe flags:
- `--canary` - publish canary version
- `--ci` - run in ci mode
- `--dirty` - allow dirty working directory
- `--build-fast` - faster builds

dangerous flags (require explicit permission):
- `--skip-checks` - skips type checking
- `--skip-tests` - skips test suite
- `--skip-build` - skips building packages

© tamagui · MIT · tamagui/tamagui

Similar skills

All skills for DevOps and infrastructure →

From the same set3

Project sponsors

Companies that keep this analytics open