safe-deploy

Original：🇺🇸 English

Translated

Enforces safe deployment practices. Use before any production deploy to prevent overwriting newer code. Activated when deploying, pushing to production, or running deploy commands.

1installs

Sourcealmeidamarcell/claude-code-skills

Added on2026-03-01

NPX Install

npx skill4agent add almeidamarcell/claude-code-skills safe-deploy

SKILL.md Content

View Translation Comparison →

Safe Deploy

Core Rule

NEVER deploy to production without first verifying the branch includes all commits from
origin/main
.

This prevents the critical bug where a feature branch deploys older code that overwrites recently merged PRs.

Before Every Deploy

Run these checks in order:

Fetch latest main
bash
```
git fetch origin main
```
Check if branch is up-to-date
bash
```
git merge-base --is-ancestor origin/main HEAD
```
- Exit code 0 = safe to deploy
- Exit code 1 = STOP, branch is behind main
If behind, show missing commits
bash
```
git log --oneline origin/main ^HEAD
```
Merge before deploying
bash
```
git merge origin/main
```
Run tests after merge
bash
```
npx vitest run
```
Only then deploy

Automated Enforcement

Projects should have a

predeploy

npm script that runs

scripts/pre-deploy-check.mjs

automatically before

npm run deploy

. If the project has this script, always use

npm run deploy

instead of calling the deploy tool directly.

When This Applies

Running
```
npm run deploy
```
Running
```
wrangler pages deploy
```
directly
Any command that pushes code to production
When the user asks to "deploy", "push to production", or "ship it"

What To Do

Always check branch status against
```
origin/main
```
first
If behind, inform the user and merge before proceeding
Run tests after merge to catch conflicts
Only deploy after tests pass
Never skip this check, even if the user says "just deploy"