secret-handling

To keep secrets out of git history, this Skill scans staged content for credential patterns and blocks commits if passwords, keys, or tokens are detected. It enforces strict avoidance of .env files and replaces real credentials with placeholders in documentation.

Credential redaction works by replacing live secrets with placeholders and redacted references when writing notes, decisions, or logs. This prevents accidental exposure of credentials from environment files while still allowing you to document required environment variables safely.

Yes, you can use template environment files safely. The Skill enforces strict avoidance of live .env files while allowing access to safe schema sources like example or template env files for reviewing environment variable requirements without exposing credentials.

The best way to block commits containing secrets is to scan staged changes for credential patterns before output. This Skill blocks commits when staged content matches passwords, keys, tokens, or private data, ensuring commit safety in collaborative Git projects.

You should use placeholder-based documentation because agents reading configuration files can accidentally expose live credentials. Replacing real values with placeholders ensures secure documentation of findings and required environment variables without leaking sensitive data into committed notes.

If staged changes match credential patterns during commit preparation, the commit is blocked entirely. The Skill detects passwords, keys, tokens, and private data in staged content to enforce strict commit safety and prevent secret exposure in git history.