Secure Coding

Use when adding API providers, environment variables, external services, logs, deployment configs, or documentation that may expose secrets.

lennney Updated 1 repo stars

File contents

Secure Coding

Rules:

  1. Never hardcode API keys, tokens, or secrets.
  2. Use environment variables or local untracked config.
  3. Provide .env.example only.
  4. Do not print secrets in logs.
  5. Do not include secrets in README, tests, screenshots, or committed files.

lennney/ticketpilot commit 8a250f1201

Frequently asked questions

npx get-skill add lennney/secure-coding