production-parity-skill-builder

Generates app-specific skills that detect and fix drift between production and non-production environments.

723|93|Updated Nov 14, 2021
One-click install
npx skills add https://github.com/citypaul/.dotfiles --skill production-parity-skill-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: production-parity-skill-builder
Source: https://github.com/citypaul/.dotfiles/tree/main/claude/.claude/skills/production-parity-skill-builder
Command: npx skills add https://github.com/citypaul/.dotfiles --skill production-parity-skill-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Local, CI, preview, and staging environments often behave differently from production, causing auth, config, and infrastructure bugs that only surface after deployment. This Skill inspects an application's repository and generates a reusable, app-specific parity skill that keeps non-production environments behaviorally aligned with production.

Core Features & Use Cases

  • Repository Inspection: Scans docs, source code, tests, CI pipelines, infrastructure manifests, and deployment config to build an evidence-backed parity map before asking any questions.
  • Targeted Questioning: Asks structured questions only for decisions the repository cannot answer, capturing each answer into the generated skill.
  • App-Specific Skill Generation: Produces a project-local skill with a parity contract, production truth sources, drift checks, fix patterns, and an explicit divergence register.
  • Use Case: A team discovers that production requires an authentik group for login while local development bypasses it. Use this Skill to generate a parity skill that documents the restriction, adds seeded IdP fixtures, and defines contract tests that fail when the enforcement drifts.

Quick Start

Ask the agent to build a production parity skill for this application by inspecting its auth, config, CI, and infrastructure setup.

Frequently Asked Questions about production-parity-skill-builder

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

FAQPage Schema
How do I keep local development environments consistent with production?

Generate an app-specific parity skill that maps production truth sources against local, CI, and preview setups. It records intentional divergences with compensating guards and defines drift checks such as contract tests, config schema validation, and preview smoke tests.

How to detect auth drift between production and staging environments?

Inspect OIDC/SAML config, required IdP groups, claims, and session policies in both environments, then add contract or E2E tests proving the production restriction is enforced. Seeded IdP fixtures that mirror production roles catch drift in normal test runs.

Where should the generated parity skill be stored?

The generated skill must live inside the target application's repository, typically under .claude/skills or .codex/skills depending on project convention. It is never placed in user-global folders like ~/.claude/skills or ~/.codex/skills.

Does this skill modify my application code or infrastructure automatically?

No. Creating the reusable skill only authorizes the skill artifact itself. Guards such as tests, fixtures, or config validation are implemented in app code only when the user explicitly requests parity fixes or authorizes the changes after reviewing the gaps.

What happens when production behavior cannot be determined from the repository?

The skill asks one targeted question at a time using the harness's structured ask-question facility, presenting evidence and recommended options. Each answer is captured into the generated skill so decisions are never left only in chat.