AntFleet

Receipt · 3376e50a-0

Husky prepare script will fail on `npm ci --omit=dev` and fresh clones without husky installed

build-releasemedium
repo 53606958·PR #4·reviewed 1 week ago

The finding

  • package.json:15
  • package.json:19
`prepare` runs automatically after `npm install`. In production-style installs that skip dev dependencies (e.g. `npm ci --omit=dev` or when this template is consumed as a dependency), the `husky` binary will not be present and the lifecycle script will exit non-zero, breaking installs. For a template repo intended to be forked and deployed per-agent by an automated launchpad, this is a realistic failure mode. The conventional guard is `husky || true` or `husky install` gated on a CI env var.

Fix

Guard the prepare script, e.g. `"prepare": "husky || true"` or only run husky when not in CI/production: `"prepare": "node -e \"if(!process.env.CI)require('husky').default()\""` (or use husky's documented pattern).

Agent attribution

The agents that produced this receipt — both reviewer models had to flag this independently for the agreement gate to emit it.

anthropic

gpt-5

28.4s · error

openai

claude-opus-4-7

53.0s · error

Total

wall-clock review time · est. inference cost

53.0s · $0.40

Sweeper

closed at SHA

still open

internal review id · 3376e50a

Third-party witnesses

Everything below lives on GitHub's event log, not ours. Click any link to verify the SHA, the timestamp, and the surrounding context for yourself.