post-deploy-env-diff

Detect production environment drift by diffing env-template defaults against on-host values.

11|1|Updated Apr 10, 2026

Search Tags:#deployment #release gating #configuration validation #operator handoff #environment drift #SSH diff

Ready to run

npx skills add https://github.com/Arcanada-one/datarim --skill post-deploy-env-diff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: post-deploy-env-diff
Source: https://github.com/Arcanada-one/datarim/tree/main/skills/post-deploy-env-diff
Command: npx skills add https://github.com/Arcanada-one/datarim --skill post-deploy-env-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents production runs from silently continuing on stale default environment values after a deploy changes the repository’s checked-in env template, by verifying on-host config state before archiving as complete.

Core Features & Use Cases

On-host env drift detection: Builds a diff of env-template default changes and checks whether the live on-host config still carries the previous defaults.
Archive-time gatekeeping: Surfaces drift in the operator handoff notes and blocks completion framing until the operator either corrects the on-host values or explicitly accepts the drift with a rationale.
Safe, read-only enforcement: Performs probing reads and does not auto-edit the host configuration, ensuring operator-controlled toggles.

Quick Start

Load post-deploy-env-diff when you update .env.example defaults and you deploy to a host that keeps its own persistent on-disk config file outside the repo.

Frequently Asked Questions about post-deploy-env-diff

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

FAQPage Schema

How do I detect environment drift after a production deployment?▼

Detect production environment drift by comparing repository env-template default changes from merge-base to head with persistent on-host env file values via SSH probing. It checks whether the live on-host config still carries previous defaults after a deploy that does not overwrite disk config.

What is the best way to block releases when on-host config is stale?▼

Archive-time gatekeeping blocks release completion framing by surfacing config drift in operator handoff notes. The deploy remains blocked until the operator either corrects the on-host values or explicitly acknowledges the drift with a rationale.

Does environment drift detection auto-correct persistent on-disk configuration files?▼

Environment drift detection uses safe, read-only enforcement and does not auto-edit the host configuration. It performs probing reads of KEY lines to ensure operators maintain full control over toggles and manual corrections.

When do I need to validate on-host env files against checked-in templates?▼

You need on-host env file validation when your deploy pipeline changes default values in checked-in env templates but does not overwrite persistent on-host config, especially for services reading disk config at boot or on signal.

Can I use SSH probing to check specific KEY lines in on-host env files?▼

Yes, SSH probing reads specific KEY lines from the persistent on-host env file to perform a per-key comparison against the new repository defaults. This identifies exactly which environment variables have drifted from the intended template state.