Scan codebases for secrets and generate .env.example scaffolds with dummy values.
npx skills add https://github.com/lshtram/core_dev --skill env-security
Please help me install this Agent Skill. Skill: env-security Source: https://github.com/lshtram/core_dev/tree/main/.agent/skills/env-security Command: npx skills add https://github.com/lshtram/core_dev --skill env-security
Secret hygiene and monitoring across code and deployments to prevent leakage of credentials and improve error observability.
Run the setup command to generate a .env.example with dummy values and verify that secret scanning and error monitoring hooks are configured.
High-intent search queries and answers about installing and using this skill.
To scan for environment secrets before committing, the setup verifies secret scanning hooks are configured and generates a .env.example scaffold with dummy values. This prevents credential leakage across code and config files during development.
To set up Sentry error monitoring hooks when scaffolding a new project, run the initialization setup. This ensures standardized error handling patterns and observability hooks are present in the project generator to catch production errors early.
The best way to maintain a .env.example file with dummy values is to use an automated scaffolding tool. This skill generates and updates the .env.example scaffold automatically, ensuring your environment variable documentation stays synchronized without exposing real secrets.
Yes, you can integrate secret scanning into your CI/CD and deployment workflows. The skill applies secret hygiene across deployment pipelines by verifying that scanning hooks and error monitoring configurations are present before code reaches production environments.
You need a .env.example scaffold to document required environment variables without exposing actual production secrets. It provides a safe template with dummy values for onboarding, preventing accidental credential leakage while ensuring developers know which configurations are required.
Yes, this secret scanning approach works with existing production environments by identifying and preventing secret leakage across codebases and live deployments. It verifies that monitoring hooks are properly configured to maintain observability and security hygiene.
az9713Initialize a project with dark code prevention directories, CLAUDE.md section, and baseline audit.
bacocoConfigure Sentry SDKs, triage errors, and set up alerts.
J03Fr0stAutomate CI/CD pipeline setup with GitHub Actions and quality gates.
kfolkesScan Python source code for security vulnerabilities using the Bandit linter.
