Deploy Guard

Name: Deploy Guard
Author: tjdwls101010

ASecurity

Guard the deploy script against being pointed at production by accident. Use when the user asks to deploy, ship, or release, and when a deploy command is being drafted. Not for local builds or test runs, which no guard covers.

4 stars
0 votes
0 copies
1 view
Added September 3, 2026

ai-agentsbash

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 3, 2026

npx -y skills add tjdwls101010/Harness-Creator --skill deploy-guard --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Deploy Guard?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tjdwls101010-deploy-guard/badge)](https://www.skillsdirectory.com/skills/tjdwls101010-deploy-guard)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: deploy-guard
description: Guard the deploy script against being pointed at production by accident. Use when the user asks to deploy, ship, or release, and when a deploy command is being drafted. Not for local builds or test runs, which no guard covers.
hooks:
  PreToolUse:
    - matcher: Bash
      hooks:
        - type: command
          command: hooks/check-target.sh
        - type: command
          command: hooks/check-target.sh
          once: true
  "PostToolUse":
    - matcher: Bash
      hooks:
        - type: command
          command: "${CLAUDE_PROJECT_DIR}/.claude/hooks/shared-audit.sh"
          args: []
---

# deploy-guard

The deploy script takes `--env` and refuses to run without it, so the ordinary
mistake is impossible. What remains is the one this hook covers: a `--env prod`
typed during a session that was only ever meant to touch staging.