Menü
Reorder a .env to mirror its .env.example, add missing keys as commented defaults, and quarantine .env-only lines. Use when the user wants to sync, mirror, align, or diff a .env against a .env.example (any project).
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Run an accessibility and keyboard navigation audit on a web page or project, then fix what it finds — audit, fix, and verify, not just a report. Use whenever the user asks about accessibility, a11y, keyboard navigation, focus styles or focus management, screen readers, ARIA, WCAG compliance, skip links, tab order, or making a site keyboard-navigable before shipping.
Run a production readiness audit on a web page or site and fix the gaps it finds — covering SEO, favicon, Open Graph / social previews, and mobile optimization. Use whenever the user asks for a production check, launch checklist, SEO or OG audit, mobile readiness check, mentions going live, or asks about favicon, meta tags, social previews, or viewport issues.
Regenerate a shareable shell-aliases JSON from the user's shell config — curated, universally-useful aliases and functions with usage frequency from shell history. Use when the user wants to refresh or update their shell aliases social media JSON.
| name | sync-env-example |
| description | Reorder a .env to mirror its .env.example, add missing keys as commented defaults, and quarantine .env-only lines. Use when the user wants to sync, mirror, align, or diff a .env against a .env.example (any project). |
| disable-model-invocation | true |
Make a .env mirror its .env.example so the two are trivially diffable, WITHOUT ever changing the user's real values.
.env and .env.example at the repo root.apps/*/.env), ask which pair before doing anything..env does not exist, ask whether to create it from .env.example verbatim, then stop..env. Preserve key, value, and quoting exactly..env.example. It is the source of truth for order/structure only..env is rewritten.Rewrite .env as three parts, in this order:
.env.example, in the SAME order.
.env: keep the .env value (uncommented), placed at the example's position..env.example and absent from .env: copy the commented line verbatim.# ===== Local extras (not in .env.example) ===== — every line that exists only in .env (orphan keys, inline alternates, commented variants), kept in their original commented/active state.- [ ] 1. Read both files fully
- [ ] 2. Build key sets: example-order list, .env-active, .env-commented, .env-only
- [ ] 3. Detect VALUE DIFFERENCES (same key active in both, different value) — collect, do NOT change
- [ ] 4. Write mirrored body + Local extras block
- [ ] 5. Diff old vs new .env; confirm no active value changed and no key was lost
- [ ] 6. Report (see below)
Ask these as ONE batched question (skip any already answered):
.env-only blocks: move to Local extras, or delete?Default if the user says "just do it": move everything .env-only to Local extras; delete nothing.
KEY (.env=<value or [secret]>, example=) — flag these explicitly; they are real behavioral mismatches, not just secrets, when the value isn't a credential..env with no example counterpart that you were unsure about.After writing, re-read .env and confirm: (a) body key order equals .env.example key order; (b) the set of active values is unchanged from the original; (c) no key disappeared except ones the user approved for deletion.