Skip to main content
skill CX Codex

pre-deploy — Claude Code skill: what it does, how to install

Runs parallel checks on builds, environment variables, and dependencies before deploying to production.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add undeadlist/claude-code-agents --skill pre-deploy -a claude-code
Open on GitHub

What pre-deploy does

The skill coordinates three sub-agents in parallel before release. First, deploy-checker validates the production build and monitors bundle size. Then, env-validator searches for leaked secrets and checks environment variables. Vulnerability scans and license audits fall to dep-auditor.

Results arrive in a single checklist. If any sub-agent fails, the gate check marks the deploy as blocked.

What it helps with

  • validate production build and bundle size
  • scan code for exposed secrets and missing environment variables
  • audit project dependencies for known vulnerabilities and licenses
  • stop production deployment when checks fail

Example prompts for the agent

  • Run pre-deploy checks before releasing to production
  • Validate build, environment, and dependencies for deployment
  • Check if the project is ready to deploy

How to install pre-deploy

1Skills CLI (Vercel)

npx skills add undeadlist/claude-code-agents --skill pre-deploy -a claude-code

2Manually: put the files in place

~/.claude/skills/pre-deploy/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/pre-deploy/

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

Questions about pre-deploy

How to install pre-deploy in Claude Code?

Run npx skills add undeadlist/claude-code-agents --skill pre-deploy -a claude-code. The skill definition will be placed in ~/.claude/skills/pre-deploy/SKILL.md.

What does pre-deploy do?

It validates project readiness before shipping to production. Three agents check builds, environment variables, and dependencies in parallel to catch blockers early.

What happens if a check fails?

The gate check marks the release status as blocked. It lists the exact blockers so you can resolve them before retrying.

Source text

SKILL.md · MIT
---
name: pre-deploy
description: Validate build, environment, and dependencies before deployment
---

# Pre-Deploy Workflow

Run before any deployment to production. All checks must pass.

## Execution (Parallel)

Spawn all three agents **in parallel**:

| Agent | Focus |
|-------|-------|
| `deploy-checker` | Build validation, bundle size, production config |
| `env-validator` | Environment variables, secrets detection, config completeness |
| `dep-auditor` | Vulnerability scan, outdated packages, license compliance |

## Gate Check

After all agents complete:
- **All pass** -> "Ready to deploy"
- **Any fail** -> "BLOCKED - Fix first" with specific blockers listed

## Expected Output

```markdown
# Pre-Deploy Checklist

## Status: READY / BLOCKED

### Build Validation (deploy-checker)
- [x] Production build succeeds
- [x] Bundle size acceptable
- [x] No build warnings

### Environment (env-validator)
- [x] All required vars set
- [x] No secrets in code
- [x] Production config valid

### Dependencies (dep-auditor)
- [x] No critical vulnerabilities
- [x] No high vulnerabilities

## Deployment Decision
READY TO DEPLOY / BLOCKED - Fix issues
```

© undeadlist · MIT · undeadlist/claude-code-agents

Similar skills

All skills for DevOps and infrastructure →

From the same set6

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor