How do I install the Reproduce The Real Build skill?

Run npx skillmds@latest add randommonicle/reproduce-the-real-build in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Reproduce The Real Build safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Reproduce The Real Build?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Reproduce The Real Build free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Reproduce The Real Build?

randommonicle (@randommonicle) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Reproduce The Real Build by randommonicle

Name: Reproduce The Real Build
Author: randommonicle

Reproduce The Real Build

Before pushing anything a CI or release pipeline will compile, run the exact production build command locally — the test runner tolerates syntax and dependency drift the release build rejects. Prove any toolchain fix by reconstructing from tracked manifests alone (npm ci into a clean directory). Triggers before pushing build-config, lockfile, or toolchain changes, and when tests pass but deployment builds fail. Does not fire on test-only changes no release pipeline compiles.

randommonicle Updated Sep 21, 2026

File contents

Reproduce the real build

Two incidents, one shape: the environment that proved the change was not the environment that ships it. A test using ESM-only syntax passed under the test runner and failed the CommonJS production tsc, blocking the deploy. A build-toolchain upgrade left the lockfile behind and kept working for two months only because both machines' node_modules had drifted ahead of it — the first clean reinstall broke everything.

The rules

Run the exact production build command locally before pushing anything the pipeline compiles — not just the test suite. The test runner tolerates what the release build rejects.
Prove toolchain fixes from the tracked manifests alone: npm ci into a clean directory (never npm install, which mutates the lockfile and hides drift). A fix proven only on the machine that produced it has not been proven — that machine's node_modules is part of the experiment.
The lockfile describes what ships. If the build only works because installed dependencies drifted ahead of it, the lockfile is silently wrong and the next npm ci is the outage.

Why

Build environments drift invisibly toward working, and the drift is per-machine; only a manifest-only reconstruction tests what CI and the next machine will actually see. Evidence: ASH CLAUDE.md Railway/Docker tsc lesson (2026-05-20); ASH LESSONS_LEARNED 2026-07-19.

Frequently asked questions