secret-configuration-security

What problem does it solve?

This Skill prevents secrets and production-sensitive configuration from being exposed anywhere in your software supply chain, from source control through builds, deployments, and documentation.

Core Features & Use Cases

• Prevents credential and secret exposure across Git history, build artifacts, container images, CI/CD logs, frontend bundles, and support tooling.
• Enforces secure redaction practices so tokens, credentials, and authorization headers are never logged, traced, or surfaced unredacted.
• Guides safe secret rotation and revocation with a create → update consumers → verify → revoke workflow that avoids incidents.

Quick Start

Use the secret-configuration-security capability to review a change that adds or modifies API keys, environment variables, KMS/secret-manager policy, or security-sensitive configuration and produce a supply-chain safe, redaction-ready plan before deployment.