Security-reviewed git commit for the ~/.claude backup repo — scans staged changes for secrets before committing. Use when committing only the ~/.claude config repo on its own; for the multi-repo "save state" checkpoint that scans and commits the knowledge base, paper-reading, agent_skills, and ~/.claude repos together, use save-to-github instead.
Installation
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Security-reviewed git commit for the ~/.claude backup repo — scans staged changes for secrets before committing. Use when committing only the ~/.claude config repo on its own; for the multi-repo "save state" checkpoint that scans and commits the knowledge base, paper-reading, agent_skills, and ~/.claude repos together, use save-to-github instead.
safe-commit
You are performing a security-reviewed git commit in the ~/.claude backup repo.
Steps
Run git -C ~/.claude diff --cached to see what is staged. If nothing is staged, run git -C ~/.claude status and stage appropriate files first (respecting .gitignore).
Security review — examine every staged change and flag anything that looks like:
Passwords, secrets, tokens, API keys (hardcoded values, not references to keyfiles)
Private key material (PEM blocks, SSH keys)
Personal credentials or auth headers with literal values
Environment variable assignments that embed a secret value
Decision:
If any high-risk item is found: stop, tell the user what was found, suggest adding it to .gitignore or removing it, and do NOT commit.
If items are low-risk or safe: summarize what will be committed and why it is safe, then proceed with the commit.
Commit with a short, descriptive message. End the commit message with:
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
