env-parity

Detect and fix environment drift between local Docker and Kubernetes deployments.

3|1|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/OmniNode-ai/omniclaude --skill env-parity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: env-parity
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/env-parity
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill env-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automatically detects and helps resolve discrepancies between your local Docker development environment and the onex-dev Kubernetes cluster, preventing "it works on my machine" issues.

Core Features & Use Cases

  • Environment Parity Checks: Compares configurations, credentials, and resource tags between local and cloud environments.
  • Drift Detection: Identifies stale ECR tags, missing Infisical paths, and credential mismatches.
  • Automated Fixing: Can automatically fix Infisical path issues.
  • Use Case: After a deployment fails with an ErrImagePull error, use this skill to quickly identify if a stale ECR tag is the culprit and then fix it.

Quick Start

Run the env-parity skill to check for critical environment drift between your local Docker setup and the onex-dev Kubernetes cluster.

Frequently Asked Questions about env-parity

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

FAQPage Schema
How do I detect environment drift between local Docker and Kubernetes?▼

To detect environment drift, run a parity check script that compares local Docker configurations against Kubernetes deployments, focusing on identifying stale ECR tags, missing Infisical paths, and credential mismatches.

What causes ErrImagePull errors in Kubernetes after a local deployment?▼

ErrImagePull errors often stem from environment drift, specifically stale ECR tags where local Docker images do not match the Kubernetes cluster expectations, requiring a drift detection check to resolve.

Can I automatically fix Infisical path mismatches between local and cloud environments?▼

Yes, you can automatically fix Infisical path issues by running an environment parity check that detects configuration discrepancies between local Docker and Kubernetes, resolving the path mismatches automatically.

Does environment parity checking support comparing credentials across infrastructure components?▼

Yes, environment parity checking compares credentials across local Docker and Kubernetes infrastructure components, identifying mismatches that cause deployment failures and preventing inconsistent development environments.

What is the best way to prevent it works on my machine issues with Kubernetes?▼

To prevent it works on my machine issues, perform environment parity checks to detect and resolve configuration drift, including stale ECR tags and credential mismatches, between local Docker and Kubernetes clusters.