env-validation
Validate .env files against .env.example or a JSON schema. Use when checking environment variables before deploy or debugging missing config.
Works with
---
name: env-validation
description: Validate .env files against .env.example or a JSON schema. Use when checking environment variables before deploy or debugging missing config.
license: MIT
---
# Environment Variable Validation
Use this skill to validate `.env` files against `.env.example` or a JSON schema. Catches missing, extra, or invalid environment variables before your app does.
## Usage
```bash
# Zero config — checks .env against .env.example
npx env-guard
# Custom paths
npx env-guard --env .env.production --example .env.example
# JSON schema validation
npx env-guard --schema env-schema.json
```
## As a Library
```typescript
import { validate } from "env-guard";
const result = validate({
env: ".env",
example: ".env.example",
});
if (!result.valid) {
console.error(result.errors);
process.exit(1);
}
```
## Key Patterns
- Zero config by default — compares `.env` against `.env.example` in the current directory
- JSON schema mode validates types, patterns, and required fields
- Returns structured errors: missing variables, extra variables, type mismatches
- Zero dependencies — no supply chain risk
- Exit code 1 on failure — safe to use in CI pipelines and pre-deploy hooksMore Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
