← ClaudeAtlas

deploy-security-gatelisted

Security gate for shipping and running products at scale. Finds exposed API keys and secrets (source, git history, frontend/mobile bundles, Dockerfiles, CI workflows, coding-agent configs), reviews AI gateway / LLM, payment and analytics integrations, flags single points of failure, and produces a go/no-go report against a fixed checklist. Use this skill whenever the user is about to deploy, release, launch, go live or cut a production build; adds or changes an integration such as OpenAI, Anthropic, Bedrock, Vertex, an AI gateway, MCP server, Stripe, Razorpay, Adyen, PayPal, Segment, PostHog, Mixpanel, Sentry or Google Analytics; asks for a security audit, pre-launch review, hardening pass, key rotation or "are any of our keys exposed"; or sets up CI/CD, Docker, Terraform or Kubernetes, even if they never say "security".
vitwit/claude-plugins · ★ 0 · DevOps & Infrastructure · score 70
Install: claude install-skill vitwit/claude-plugins
# Deploy security gate This skill enforces one checklist: **no key is ever exposed, and no single failure takes the product down**. It runs in three passes: 1. An automated scan with `scripts/scan.py`, which is fast, deterministic and read-only. 2. A code review of each detected integration, guided by `references/integrations.md`. 3. A manual gate for everything that can't be seen from the repo, such as provider dashboards, rotation, backups and drills. These items come from `references/checklist.md`. The scan alone is not a pass. It covers roughly a third of the checklist. The value of this skill is in walking all three passes and being honest about what was verified and what still needs a human to confirm. ## Workflow ### 1. Scope Work out what is shipping: - the repo root - frontend or mobile build output, if any - the deployment target, such as containers, serverless or Kubernetes - whether this is a first launch, a new integration or routine maintenance If the user named a specific change, such as "adding Stripe", focus the review on it. Still run the full scan, because a leak elsewhere blocks the release just the same. ### 2. Run the scanner ```bash python3 <skill-dir>/scripts/scan.py <repo> --history ``` - Add `--build-dir <dir>` for each built bundle (`dist`, `.next/static`, an unzipped APK/IPA). Shipped bundles are where "public" keys turn out to be secret ones. Common build directories are detected automatically; build the app first if none exist. - `--en