setup-tool-bun

Configure Bun as the package manager and enforce version and script policies.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/tachiiri-org/agent-ops --skill setup-tool-bun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-tool-bun
Source: https://github.com/tachiiri-org/agent-ops/tree/main/.codex/skills/setup-tool-bun
Command: npx skills add https://github.com/tachiiri-org/agent-ops --skill setup-tool-bun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that your repository is correctly set up to use Bun as its package manager, aligning with defined version policies and script execution standards.

Core Features & Use Cases

  • Bun Integration: Establishes Bun as the primary tool for package installation and script running.
  • Version Management: Enforces the expected Bun version as defined in your project's guidelines.
  • Use Case: When onboarding a new developer or setting up a CI/CD pipeline, this Skill guarantees that Bun is the package manager and that all scripts are configured to run with bun run.

Quick Start

Run the setup-tool-bun skill to configure Bun for this repository.

Frequently Asked Questions about setup-tool-bun

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Bun as the package manager for my repository?

Configuring Bun for your repository involves verifying its installation, checking package.json existence, and aligning script commands to use 'bun run' for execution. The setup ensures adherence to baseline Bun version policies.

What do I need to set up a CI/CD pipeline for Bun-managed projects?

You need to verify Bun's presence and ensure package.json exists in your repository. The configuration then aligns script execution commands to use 'bun run', ensuring CI/CD pipeline adherence to baseline version policies.

How does script execution work when using Bun as a package manager?

Script execution with Bun requires aligning package.json commands to use 'bun run' instead of other package manager commands. This ensures all repository scripts execute through Bun, adhering to defined version policies and execution conventions.

Can I use this configuration for new project setups with Bun?

Yes, this configuration applies to new project setups and CI/CD pipelines. It verifies Bun's presence and package.json existence, aligning script execution commands to use 'bun run' for proper integration from the start.

Why is verifying Bun's presence required for repository configuration?

Verifying Bun's presence is required to enforce baseline version policies and guarantee script execution commands can be aligned to use 'bun run'. It confirms the package manager is installed before configuring your repository.