What problem does it solve? Teams building secret-management tooling risk leaking credentials through logs, hardcoded values, misconfigured CI/CD workflows, or unvalidated inputs. This Skill provides concrete security guardrails for the Envilder project so code reviews and new features consistently follow safe secret-handling practices. ## Core Features & Use Cases - Secret Handling Rules: Defines how secrets are stored, masked, and logged across the CLI, GitHub Action, SDKs, and website, including Secretlint enforcement on every lint run. - CI/CD Credential Hygiene: Mandates OIDC-based AWS authentication, minimal workflow permissions, and SHA-pinned GitHub Actions instead of long-lived access keys. - Input Validation & Supply Chain Safety: Specifies validation rules for CLI options and SDK inputs, dependency pinning via lock files, and a pre-merge security checklist. - Use Case: When reviewing a pull request that adds a new CLI option accepting a file path, apply this Skill to ensure path traversal validation, domain-specific errors, and no unsanitized shell interpolation. ## Quick Start Review this pull request against the common-security guardrails and flag any secret handling, input validation, or workflow permission issues.