# Bun

> Bun runtime and package manager guidance. Use when running Bun commands, managing dependencies, executing scripts, using bunx, running tests, or troubleshooting Bun-specific behavior in JS/TS projects.

- Skill: `justbecauselabs/bun` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add justbecauselabs/bun`
- Raw SKILL.md: https://api.skillmd.com/api/skills/justbecauselabs/bun/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: justbecauselabs (https://skillmd.com/u/justbecauselabs)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/justbecauselabs/bun

---


# Bun

## Overview
Use this skill to operate Bun projects and choose the correct Bun command for installs, scripts, and tests. Keep guidance consistent with the project's existing scripts and configuration.

## Workflow
1. Check for Bun indicators: `bun.lockb`, `bunfig.toml`, or `package.json` scripts that mention Bun.
2. Prefer project scripts over ad-hoc commands; use `bun run <script>` for `dev`, `build`, or `test` when defined.
3. Use Bun's native tools only when the repo expects them (for example, `bun test` with Bun's test runner).
4. Avoid editing lockfiles by hand; update dependencies via Bun commands.

## Command Reference
- Read `references/bun.md` when you need concrete command lines, testing guidance, or dependency workflows.

## Notes
- Keep commands explicit and predictable; avoid clever flags unless the project already uses them.
- If the repo uses another tool (pnpm, yarn, npm), follow that tool instead of forcing Bun.