Version Packages

[arkenv-bot]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@arkenv/cli@0.0.5

Patch Changes

• Add agent skill support #945 63d6237 @yamcodes

  The CLI now has a new --agent flag that lets the ArkEnv agent skill interact with it in a token-sensitive way. The skill has been updated to support this new mode.

  Also, the CLI will now suggest to install the agent skill for you when in non---agent mode.

  Read more in the ArkEnv CLI docs.

• Improve "done" message text #954 fe10ef4 @yamcodes

  The output now clearly distinguishes between the local scaffolding and the AI-powered refinement:

      1 │
      2 ◇  Next steps ─────────────────────────────────────────────────────────────────╮
      3 │                                                                              │
      4 │  1. Check ./src/env.ts and refine your environment schema.                   │
      5 │  2. Import and use: import { env } from "./src/env"                          │
      6 │  3. (Recommended) Install the AI skill: pnpm dlx skills add yamcodes/arkenv  │
      7 │     Then run /arkenv inside your AI assistant to finish.                     │
      8 │                                                                              │
      9 ├──────────────────────────────────────────────────────────────────────────────╯
     10 │
     11 └  ⛯ ArkEnv scaffolding complete. Happy coding!
  

• Install framework plugins #948 1dca74c @yamcodes

  The ArkEnv CLI now installs framework plugins as part of the scaffolding process if a relevant runtime/framework is selected.

• Passthrough --yes and --quiet to underlying process #952 10cbb7d @yamcodes

  The ArkEnv CLI will now pass the flags --yes and --quiet to underlying processes.

  This means that if you run:

  pnx @arkenv/cli init --yes

  It would now use the recommended settings and avoid prompts even in sub-processes like the Vercel Skills process to add the ArkEnv skill.

  Similarly, if you run:

  pnx @arkenv/cli init --quiet

  You will not be exposed to the underlying Vercel Skills output, except for errors which are buffered in memory. (Resolves on exit code 0, discarding buffered output on success)

[pkg-pr-new]

Open in StackBlitz

arkenv

npm i https://pkg.pr.new/arkenv@950

@arkenv/bun-plugin

npm i https://pkg.pr.new/@arkenv/bun-plugin@950

@arkenv/cli

npm i https://pkg.pr.new/@arkenv/cli@950

@arkenv/fumadocs-ui

npm i https://pkg.pr.new/@arkenv/fumadocs-ui@950

@arkenv/vite-plugin

npm i https://pkg.pr.new/@arkenv/vite-plugin@950

commit: b27e93f

[arkenv-bot]

📦 Bundle Size Report

Package	Size	Limit	Diff	Status
arkenv	1.73 kB	1.95 kB	<0.1%	✅
arkenv/standard	1.01 kB	1.07 kB	-41.6%	✅
arkenv/core	441 B	500 B	-75.1%	✅
@arkenv/bun-plugin	2.4 kB	2.44 kB	<0.1%	✅
@arkenv/vite-plugin	1.91 kB	2.93 kB	<0.1%	✅

✅ All size limits passed!

[arkenv-bot]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (Asia/Almaty)
arkenv	Ready	Preview, Comment	May 12 2026, 7:22 PM (Asia/Almaty)