← ClaudeAtlas

shipcheck-secretslisted

Scans a project, and optionally its recent git history, for leaked secrets (AWS, GitHub, Slack, Stripe and Google keys, private keys, JWTs, database URLs with passwords, generic password and token assignments, high-entropy strings) with masked output, then runs a rotation-first response: assume the secret is burned, revoke it first, clean history only afterwards and only if the user wants. Use when the user says "scan for secrets", "did I commit an API key", "check this before I push", "I pushed a token by accident", "is my .env safe", "rotate this key", or "find leaked credentials".
vivekbhange-hub/ship-check-skill · ★ 0 · Code & Development · score 75
Install: claude install-skill vivekbhange-hub/ship-check-skill
# shipcheck-secrets: find the leak, then rotate before anything else A secret that reached a commit, a log or a chat is burned. Deleting the line does not un-leak it: bots scrape public pushes within minutes, and every clone and fork keeps a copy. So this skill finds the secret with `secrets_scan.py` (output always masked), and then puts rotation ahead of cleanup. ## Inputs - A project folder (default `.`). Git is used for the file list when the folder is a repo. - Optional: how many commits of history to scan (`--history`, default 50 commits). - Commands below say `python3`; on Windows use `python` (or `py -3`). ## Outputs - A masked findings list: `file:line`, rule id, severity, name, `AKIA****3H`-style value and a fingerprint (`fp:...`) that is stable across runs and used for allowlisting. - A rotation plan per provider, in order, and an optional history cleanup plan. - Optional `.shipcheck-ignore` entries for confirmed false positives. ## Steps 1. **Confirm authorization.** Only scan a project the user owns or has permission to audit. Scanning someone else's repository for credentials is not what this skill is for. 2. **Scan.** ``` python3 "${CLAUDE_SKILL_DIR}/secrets_scan.py" . --fail-on never python3 "${CLAUDE_SKILL_DIR}/secrets_scan.py" . --history --history-commits 200 --fail-on never ``` Use `--json` when you need to process the result. The second form also lists secrets that were committed and later deleted: they are still in history,