Skip to content
PluginDeveloper & DevOps Tools

Ship Guard

Free Claude Code safety net: blocks edits to .env, keys and lockfiles, force pushes, hard resets, deletes outside the project and curl | sh.

New listingUpdated Oct 29, 2026Marketplace Founder

About Ship Guard

Claude Code is most useful when you let it run commands. It is also then that one wrong command costs the most: a force push over a teammate's work, a reset --hard on a day of changes, an rm -rf one folder too high, or a key written into the wrong file.

Ship Guard adds a PreToolUse hook that checks every shell command and file edit before it runs. It blocks edits to .env files, private keys and lockfiles; force pushes (and --force-with-lease to protected branches); git reset --hard, git clean -f and whole-tree restores; recursive deletes outside the project, of the root or of .git; and downloaded scripts piped into a shell. Each block tells Claude why, and gives a safer alternative to use instead.

When you mean it, type /allow-once <reason>. The next matching action goes through once within 10 minutes, and every block and override is logged. /guard-status shows what is protected and runs a self-test. /preflight is a pre-release checklist: tests, lint, build, version bump, changelog, risky migrations, undocumented env vars, focused tests and debug leftovers.

It was tested on 102 sample commands in Bash and PowerShell, on Windows and Linux paths.

Limits: it reads command text, so it cannot see inside scripts or git aliases. It does not stop reads of .env. It is a safety net, not a security boundary.

Highlights

  • Blocks force push, reset --hard and curl | sh
  • Protects .env files, private keys and lockfiles
  • Stops recursive deletes outside the project
  • Every block explains a safer alternative
  • Explicit, logged one-time overrides
  • /preflight release checklist with a verdict
  • safety
  • git
  • hooks
  • guardrails
  • release checklist
  • env files
  • devops