gemini-cli-cli

Migrate gemini-cli Node.js toolchain scripts, tests, SEA, and Docker to Bun.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/aphrody-code/n2b --skill gemini-cli-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gemini-cli-cli
Source: https://github.com/aphrody-code/n2b/tree/main/skills/gemini-cli-cli
Command: npx skills add https://github.com/aphrody-code/n2b --skill gemini-cli-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you replace the Node.js-based CLI toolchain of gemini-cli (npm/npx/tsx/cross-env/vitest, plus SEA, lockfile, and Docker sandbox) with Bun runtime equivalents so your project builds and runs cleanly under Bun.

Core Features & Use Cases

  • Migrates CLI execution paths: rewrites root package.json scripts (node/npm/npx/tsx/cross-env) to Bun commands and updates related tooling entrypoints.
  • Covers monorepo/workspaces: validates and preserves Bun-compatible workspaces behavior and dependency installation via bun install/filters.
  • Modernizes test and distribution strategy: moves vitest tests toward bun:test patterns and replaces Node SEA with bun build --compile, then updates sandbox Docker build steps.
  • Handles operational edge constraints: explicitly keeps packages/vscode-ide-companion on Node to avoid breaking the VSCode extension runtime.

Quick Start

Tell the AI to migrate the CLI toolchain for the gemini-cli target: run n2b on tests/targets/gemini-cli with the provided ignore rules, then execute the skill migration workflow to rewrite scripts, swap test strategy, replace SEA, and update sandbox Docker accordingly.

Frequently Asked Questions about gemini-cli-cli

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

FAQPage Schema
How do I migrate a Node.js CLI toolchain to Bun?

Migrating a Node.js CLI toolchain to Bun involves rewriting package.json scripts to use bun, bunx, and bun build --compile, translating vitest tests to bun:test, and updating Docker sandbox builds. This Skill automates that entire migration process for gemini-cli projects.

How do I convert vitest tests to bun:test in a monorepo?

Converting vitest tests to bun:test in a monorepo requires translating vitest patterns to bun:test equivalents while validating workspace dependencies. This Skill handles that translation while preserving Bun-compatible workspaces behavior and filtering out Node-only packages like the VSCode companion.

Does migrating to Bun break VSCode extension runtime compatibility?

Migrating to Bun does not break VSCode extension compatibility when you explicitly exclude Node-only packages. This Skill keeps packages/vscode-ide-companion on Node to avoid breaking the VSCode extension runtime while migrating the rest of the monorepo.

How do I replace Node SEA with bun build --compile for CLI distribution?

Replacing Node SEA with bun build --compile for CLI distribution requires updating your build scripts to use Bun's native compilation. This Skill modernizes your distribution strategy by replacing Node SEA packaging with bun build --compile and updating sandbox Docker build steps accordingly.

What is the best way to handle workspaces and lockfiles when switching to Bun?

Handling workspaces and lockfiles when switching to Bun requires validating workspace configurations and migrating dependency installation to bun install. This Skill covers monorepo workspaces by preserving Bun-compatible behavior and updating infrastructure files used to distribute the CLI.

Can I automate npm to Bun script migrations across a monorepo?

Automating npm to Bun script migrations across a monorepo is possible by rewriting root package.json scripts that use node, npm, npx, tsx, and cross-env to Bun commands. This Skill executes the migration workflow in one run to swap scripts, test strategies, and sandbox Docker configurations.