env-drift-check
Skill1 starsChanged 3 months agoMITView on GitHub
Detect drift between env examples, docs, and real config needs. Use when onboarding fails, deploy misses vars, or Chinese "环境变量", ".env", "配置对不上", "env drift".
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- sriptcollector/toolbay-skillstheir own version, first seen Jul 28, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- sriptcollector/toolbay-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-diff-ship-checkSkill
- customer-bug-to-failing-testSkill
- dead-code-safe-deleteSkill
- feature-flag-lifecycleSkill
- flake-vs-bug-triageSkill
- minimal-repro-packSkill
- secret-redact-before-aiSkill
- using-ship-guard-skillsSkill
The file
Files
Env Drift Check
Overview
Compare .env.example, README setup, code process.env / config reads, and CI secrets list for missing or undocumented keys.
Steps
- Collect sources: example env, docs, code references, deploy manifests.
- Build union of required keys.
- Mark: documented | in-example | in-code | in-CI | missing.
- Flag secrets that appear in examples as real values.
- Produce fix list: add to example (empty), docs, or remove dead reads.
Exit criteria
- Matrix of keys
- Gaps listed
- Secret leakage in examples checked
- Remediation list
Anti-patterns
- Committing real
.env - Docs that say “set up env” with no key list
Output template
## Env drift
| key | code | example | docs | CI | gap |
|-----|------|---------|------|-----|-----|
### Fixes
- [ ] ...Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.