Generate a sanitized .envrc.sample and git-ignore .envrc.
npx skills add https://github.com/doesitscript/dotfile-vnext --skill sanitize-envrc
Please help me install this Agent Skill. Skill: sanitize-envrc Source: https://github.com/doesitscript/dotfile-vnext/tree/main/.cursor/skills/sanitize-envrc Command: npx skills add https://github.com/doesitscript/dotfile-vnext --skill sanitize-envrc
Managing secrets in project environment files (.envrc) can expose sensitive data if committed or shared; this skill creates a sanitized .envrc.sample and ensures .envrc is git-ignored.
Run this skill at the repository root to generate a safe .envrc.sample and ensure .envrc is ignored.
High-intent search queries and answers about installing and using this skill.
To sanitize a .envrc file before committing, this skill reads the file, identifies secret variables by name patterns like KEY or TOKEN, and generates a .envrc.sample with placeholders. It also ensures .envrc is added to .gitignore to prevent accidental exposure.
The best way to generate a sample .envrc file safely is by using a sanitization process that detects common secret names and replaces their values with obvious placeholders, ensuring new projects can bootstrap securely without leaking sensitive configuration data.
Secret detection for environment configuration files works by scanning variable names for patterns such as SECRET, TOKEN, KEY, and PASSWORD. When matches are found, the actual values are substituted with obvious placeholders in the output file.
Yes, you can automatically add .envrc to .gitignore to prevent accidental commits. This skill checks the repository's .gitignore and updates it when needed, ensuring your environment configuration is ignored by version control.
This sanitization tool targets common secret variable naming conventions like KEY, SECRET, TOKEN, and PASSWORD. It scans these patterns within your .envrc file to accurately identify which values require placeholder substitution.
You should use a .envrc.sample file because committing a .envrc file risks exposing sensitive data like API keys and passwords. A sanitized sample provides the required structure for team members without sharing actual secret values.
CsHengApply security guardrails for credential management and secret rotation across services.
tnezInitialize the .docent directory structure and configuration for new projects.
elasticdotventuresAutomate loading of per-project environment variables via direnv and dotenv with Rust validation.
OirancaScan repositories for common secret patterns and environment file hygiene issues.
