Installed.
@shipcheck/env-secrets-check is ready in your project.
Use it
Ask Claude for the job it does, in your own words. Check your repo for leaked secrets before you push or launch: .env files git tracks or will pick up, .env files hiding in git history, server keys behind NEXT_PUBLIC_ or VITE_ prefixes that ship to the browser, provider key shapes (Stripe, AWS, GitHub, OpenAI, Anthropic, Supabase service_role), and passwords hardcoded in code. Reports names and redacted hints, never the values.
Keep it current
slashclone updateUpdates that ask for new access need your approval again.
Remove it
slashclone remove @shipcheck/env-secrets-checkDid it work?
A like tells the author, and helps the next person find it.
Share it
https://slashclone.dev/@shipcheck/env-secrets-check