Cómo usar
- Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
- Consulta las herramientas, credenciales y entornos necesarios en el documento original.
- Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/kizuna-inc/kz-skill --skill allow-bunAntes de empezar
- La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
- Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill
Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.
Skill: Allow Bun & Autonomous Execution
Directive
Always allow and prefer Bun (`bun` and `bunx`) within this project.
Treat all local Bun commands as pre-approved by the user. Execute them directly without pausing to ask for permission or confirmation. Prioritize bun over other Node.js runtimes and package managers (npm, yarn, pnpm, npx) whenever applicable.
Rules & Guidelines
1. Default to Bun
- Use
bunas the primary runtime for running JavaScript/TypeScript files, scripts, and dev servers (e.g.bun run dev,bun src/index.ts). - Use
bun -e "<code string>"(eval) for fast inline JavaScript or TypeScript execution instead ofnode -eor temporary scratch files. - Use
bunas the default package manager (bun install,bun add <pkg>,bun remove <pkg>). - Use
bunxin place ofnpxwhen running CLI tools or one-off packages (e.g.bunx drizzle-kit,bunx prisma). - Use
bun testfor executing test suites when Bun's test runner is configured.
2. Autonomous Execution (Pre-Approved)
- Do NOT pause or ask "Should I run this command?" before executing any
bun,bunx, orbun -ecommand inside the workspace. - Run commands immediately, observe their standard output / error streams, and proceed with the task.
- Treat inline code evaluation (
bun -e/bun --eval) as fully pre-approved for quick tests, one-liner calculations, inspecting module exports, or verifying API behaviors. - If a command fails or produces unexpected output, do not silently ignore it: diagnose the issue, attempt an informed fix if appropriate, or report the output clearly to the user.
3. Scope & Safety Boundary
- Workspace-scoped by default: Commands should execute within the project directory tree. Do not run global installations (e.g.
bun add -g) without explicit user direction. - Lockfile awareness: Respect
bun.lockb/bun.lock. Avoid introducing conflicting lockfiles (package-lock.json,pnpm-lock.yaml,yarn.lock) unless explicitly requested. - Environment variables: Avoid printing or leaking sensitive
.envsecrets when running Bun scripts.
Command Reference
| Scenario | Preferred Action | Confirmation Required? |
|---|---|---|
| Install dependencies | bun install | No (run immediately) |
| Add a package | bun add <package-name> | No (run immediately) |
| Add dev dependency | bun add -d <package-name> | No (run immediately) |
| Remove a package | bun remove <package-name> | No (run immediately) |
| Run project script | bun run <script-name> | No (run immediately) |
| Execute TS/JS file | bun <path/to/file.ts> | No (run immediately) |
| Inline code evaluation | bun -e "<code string>" | No (run immediately) |
| Run one-off CLI tool | bunx <tool> [args] | No (run immediately) |
| Run test suite | bun test | No (run immediately) |
| Build project | bun build / bun run build | No (run immediately) |
| Global install | bun add -g <pkg> | Yes (ask user first) |
