config-consistency-checker

Compare key-value pairs across configuration files and deployment manifests to detect drift.

1|2|Updated Mar 10, 2026

Search Tags:#devops #consistency #deployment #drift detection #configuration #auditing

Ready to run

npx skills add https://github.com/santosomar/general-secure-coding-agent-skills --skill config-consistency-checker-santosomar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: config-consistency-checker
Source: https://github.com/santosomar/general-secure-coding-agent-skills/tree/main/skills/devops/config-consistency-checker
Command: npx skills add https://github.com/santosomar/general-secure-coding-agent-skills --skill config-consistency-checker-santosomar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies and flags inconsistencies across configuration files, environments, and deployment manifests, preventing "works in staging, broken in prod" scenarios.

Core Features & Use Cases

Environment Comparison: Detects missing keys or drifted values between configuration files (e.g., staging.yaml vs. production.yaml).
Code vs. Config Audit: Identifies dead configuration keys (in file, never read) or unbacked reads (read by code, never in config).
Deployment Drift Detection: Compares application configuration against deployment manifests (e.g., Kubernetes ConfigMaps).
Type Mismatch Alerts: Flags values that do not match expected types or schemas.
Use Case: Before deploying to production, use this Skill to ensure that the staging and production configurations are aligned, catching potential issues caused by manual edits or incomplete rollouts.

Quick Start

Use the config-consistency-checker skill to compare staging.yaml and production.yaml for any inconsistencies.

Frequently Asked Questions about config-consistency-checker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect configuration drift between staging and production environments?▼

To detect configuration drift between staging and production, you can compare key-value pairs across files like staging.yaml and production.yaml to classify differences as intentional changes or drift. The checker flags missing keys, drifted values, and type mismatches before deployment.

What is configuration drift and how does it cause deployment failures?▼

Configuration drift occurs when environment files or deployment manifests like Kubernetes ConfigMaps become inconsistent over time due to manual edits. This drift causes deployment failures when missing configuration keys or type mismatches break applications moving from staging to production.

Can I audit code against configuration files to find dead or missing keys?▼

Yes, you can audit code against configuration files to find dead configuration keys that exist in files but are never read by code, and unbacked reads where code reads configuration keys that are missing from the files.

How do I check Kubernetes deployment manifests against application configuration?▼

You can check Kubernetes deployment manifests against application configuration by comparing the flattened key-value pairs and types in your ConfigMaps against your application config files to identify and flag any deployment drift or mismatches.

What is the best way to prevent works in staging but broken in prod scenarios?▼

The best way to prevent works in staging but broken in prod scenarios is to run a consistency check comparing flattened key-value pairs and types across configuration files and deployment manifests to catch missing keys and type mismatches before production deployment.