# Validate Deployment Configuration Safely

Configuration errors can cause failed deployments, security gaps, and inconsistent environments. This skill designs schemas, tests, migrations, runtime checks, and clear configuration documentation.

## Install

```bash
npx skillstore add sickn33/deployment-validation-config-validate
```

## Metadata

- Status: approved
- Slug: sickn33-deployment-validation-config-validate
- Skillstore revision: r2
- Version status: missing
- Tree hash: 5e8920ce7a22a5e68d84f92ac684fedb97c9300642e8751999d7cb2a1dfb53d9
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/deployment-validation-config-validate
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem, env\_access
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/sickn33-deployment-validation-config-validate
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-deployment-validation-config-validate/manifest

## Capabilities

- Analyzes JSON, YAML, TOML, INI, environment, and JavaScript configuration locations for validation needs and secret patterns.
- Designs JSON Schema validation with Ajv formats for HTTPS URLs, ports, hostnames, and durations.
- Defines different validation rules for development, staging, and production environments.
- Creates configuration test plans and Jest examples for valid and invalid settings.
- Proposes runtime file watching, versioned configuration migrations, and encrypted value handling.
- Generates configuration reference documentation from schema properties and examples.

## Use Cases

- Prepare a Deployment Gate: Create environment-aware schema checks and tests that reject unsafe configuration before release.
- Add Typed Application Settings: Define required fields, formats, defaults, and useful validation errors for an application.
- Review Configuration Security: Identify secret exposure, weak production defaults, unsafe URLs, and missing encryption controls.

## Prompt Templates

### Inventory Configuration Risks

```
Review configuration files under {{project_path}}. Identify formats, environments, missing validation, and consistency risks. Do not reveal secret values.
```

### Design a Validation Schema

```
Create a validation plan for {{config_name}}. Define required fields, types, ranges, secure formats, defaults, and readable error messages.
```

### Build Environment Tests

```
Design tests for development, staging, and production configuration. Cover valid settings, boundary values, forbidden production options, and missing secrets.
```

### Plan Runtime Validation and Migration

```
Design runtime reload validation and migrations from {{current_version}} to {{target_version}}. Include rollback, path boundaries, secret handling, and failure behavior.
```

## Limitations

- The examples are illustrative and omit several helper methods, loaders, type guards, and production error handling.
- The skill does not verify real configurations unless the agent receives approved workspace access and relevant files.
- Secret detection is pattern-based and may flag harmless names or read sensitive environment files.
- The encryption and file-watching examples require security review before production use.

## Best Practices

- Approve a narrow configuration root and redact secret values before analysis or reporting.
- Validate configurations before deployment, after migration, and before accepting runtime reloads.
- Test environment rules with valid cases, boundary values, missing fields, and forbidden production settings.

## Anti Patterns

- Do not scan an entire home directory or repository for environment files without explicit approval.
- Do not copy illustrative encryption code into production without independent cryptographic review.
- Do not reload invalid configuration or continue silently after production validation fails.

## Security Audit

- Audited at: 2026-07-23T22:06:06.808\+00:00
- Summary: Most command, environment, certificate, and reconnaissance alerts are syntax or identifier false positives. The guidance intentionally discovers and reads .env files and demonstrates persistent file watching. Its encryption example derives keys with a fixed salt, weakening password-based key isolation.

## Stats

- Views: 169
- Downloads: 11
- Favorites: 0
- Popularity score: 0