Use Bun frozen-lockfile installs in CI with Claude Code

Use bun-install to choose an install mode and verify CI follows the committed dependency resolution.

Install in Claude Code

Claude Code, Bun, and a local practice project with a committed lockfile.

Open the pinned GitHub source below and retrieve the `typescript-plugin/skills/bun-install/` directory from that revision.
Copy it into `.claude/skills/bun-install/` in your project, keeping `SKILL.md` and its companion files together.
Open Claude Code in the project root and enter `/bun-install` followed by the example task.

Example task

Copy a sample repo with package.json and bun.lock. Ask for a CI command and verification plan. Compare the lockfile before and after and try a manifest change in a separate copy.

What to check

The plan uses bun install --frozen-lockfile, leaves the lockfile unchanged on success, and expects an error when the manifest and lockfile disagree.

Original SKILL.md on GitHub · Updated 2026-11-11

Frequently asked question

Why use a frozen lockfile in CI?

It makes CI reject disagreement between the manifest and lockfile. Intentional dependency updates can change the lockfile through the review workflow.