env-deploy

Standardize environment variable and secret management across deployments using Infisical.

Updated May 7, 2026
One-click install
npx skills add https://github.com/johinsDev/loyalty-app --skill env-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-deploy
Source: https://github.com/johinsDev/loyalty-app/tree/main/.claude/skills/env-deploy
Command: npx skills add https://github.com/johinsDev/loyalty-app --skill env-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents “missing env var” failures and inconsistent deployments by making Infisical the single source of truth for every secret across dev, preview, and prod.

Core Features & Use Cases

  • Single source of truth for secrets: centralizes configuration in Infisical and ensures web/admin/jobs/partykit receive values from Infisical rather than ad-hoc entries.
  • Reproducible local + CI-safe workflows: supports local injection (including preview env overrides) while safely falling back when Infisical isn’t set up (non-breaking onboarding).
  • Preview pipeline wiring with anonymized DBs: coordinates PR-based preview database creation, migration, and Vercel env pinning, including outbox-based third-party behavior.

Quick Start

Ask the skill to walk you through setting up or rotating an environment variable end-to-end from Infisical to the specific runtime(s) that consume it.

Frequently Asked Questions about env-deploy

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

FAQPage Schema
How do I stop missing environment variable failures during Vercel preview deployments?

To stop missing environment variable failures during Vercel preview deployments, you centralize secrets in Infisical as the single source of truth and wire it into your CI and PR preview flows, ensuring web, admin, and jobs receive correct values without manual drift.

How do I rotate secrets across dev, preview, and prod deployments without causing inconsistencies?

To rotate secrets across dev, preview, and prod deployments without causing inconsistencies, you update the values in Infisical and let the standardized pipeline propagate them to Vercel and related runtime processes. This maintains a single source of truth and prevents ad-hoc configuration discrepancies.

Does Infisical work with CI CD pipelines for reproducible local environment injection?

Yes, Infisical works with CI CD pipelines to provide reproducible local environment injection using a script like with-infisical.sh. It safely falls back to local configurations when Infisical is not set up, ensuring non-breaking onboarding for new developers.

What is the best way to manage environment variables for a PR-based preview database?

The best way to manage environment variables for a PR-based preview database is to coordinate preview database creation, migration, and Vercel environment pinning through a centralized secrets manager like Infisical. This approach applies consistent folder-to-env scoping and handles outbox-based third-party behavior.

Why does my deployment pipeline have environment variable drift between web, admin, and jobs?

Your deployment pipeline has environment variable drift because runtimes like web, admin, and jobs are receiving ad-hoc entries instead of pulling from a single source of truth. Centralizing configuration in Infisical ensures every runtime consumes identical, authoritative secret values.