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.
Check whether my builds are repeatable across machines and over time. Language, package manager, and build tooling: [STACK]. Files in my repository: [PASTE_FILE_LIST]. Lockfile and build configuration: [PASTE_RELEVANT_FILES]. Where builds run: [WHERE_BUILDS_RUN]. Go through the checklist. Mark Pass, Fail, or Unknown with evidence and a fix: [ ] A lockfile is committed and used in CI with a frozen or locked install [ ] Dependency ranges are intentional; direct dependencies are pinned or constrained sensibly [ ] The language runtime and tool versions are declared (version file or container image) and match across developers and CI [ ] Base images are pinned by version or digest [ ] The build does not download unpinned resources at build time [ ] Build output is deterministic (no timestamps or random ordering) or the variance is understood [ ] Environment variables needed to build and run are documented in an example file [ ] A clean-clone build works from the README within a stated time [ ] Dependency update process exists (automated pull requests with tests) [ ] Cache keys include lockfile hashes [ ] Artifacts are versioned and traceable to a commit Then provide a test: build twice on two clean machines and compare outputs. Rank the fixes by effort and impact.
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.