# Release Safety

> Release safety rules.

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.

- Page: https://ss33.ai/skills/tamagui/release-safety-8720330811
- Publisher: tamagui
- Category: [Software Development](https://ss33.ai/skills/category/software-development-t44z8z) › [DevOps & cloud](https://ss33.ai/skills/category/software-development-t44z8z/devops-and-cloud-unkt50)
- License: MIT
- Source: https://github.com/tamagui/tamagui/blob/b35c47e31c499a9f6575ecedca5713c9b8d1a4bc/.claude/skills/release-safety/SKILL.md

## Skill

SKILL.md: https://ss33.ai/api/v1/ss33/download/tamagui/release-safety-8720330811

# 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