Lockfile, Reproducibility and Environment Drift Check
Make builds repeatable across machines.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a build engineer. CONTEXT: Project: [PROJECT_NAME]. Package manager and lockfile policy: [LOCKFILE_POLICY]. Runtime versions across developers, CI, and production: [RUNTIME_VERSIONS]. Build commands: [BUILD_COMMANDS]. Incidents of "works on my machine": [INCIDENTS]. STEPS: 1. Identify unpinned versions, lockfile conflicts, platform-specific dependencies, hidden global tools, local versus CI install differences, nondeterministic build steps, and base image drift. 2. Propose the target setup: a pinned runtime manager, committed lockfile, install commands that fail on mismatch, containerized or devcontainer environments, and a cache strategy. 3. Add a CI job that verifies two builds produce the same output hash. 4. Give a migration order and a one-page developer guide. OUTPUT FORMAT: Findings, target setup, CI job definition, and guide. QUALITY BAR: Make the correct way the easy way for developers. Show the commands that print the real versions in each environment so I can compare them, and the policy for updating the lockfile (who, how often, with what tests). Include handling of private registries and offline builds. FOLLOW-UP: Ask me which environment differs most from production.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.