CLI Fix done story#954
Conversation
🦋 Changeset detectedLatest commit: 4fa90ff The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
WalkthroughThis PR enhances the ArkEnv CLI's post-scaffolding user experience by adding a conditional logging method to the Logger class and refactoring init command messaging to use multi-line dedent formatting. The changeset documents the patch release with improved guidance text distinguishing local scaffolding from AI refinement. ChangesCLI messaging and logger enhancements
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
arkenv
@arkenv/bun-plugin
@arkenv/cli
@arkenv/fumadocs-ui
@arkenv/vite-plugin
commit: |
📦 Bundle Size Report✅ All size limits passed! |
|
Of course this needs a changeset. |
|
🤖 Hi @yamcodes, I've received your request, and I'm working on it now! You can track my progress in the logs for more details. |
|
🤖 I'm sorry @yamcodes, but I was unable to process your request. Please see the logs for more details. |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.changeset/great-deer-check.md:
- Around line 9-21: The fenced code block that contains the "Next steps" ASCII
art is missing a language identifier which triggers markdownlint MD040; fix this
by changing the opening fence from ``` to ```text so the block is labeled as
plain text (the block that starts with the "Next steps" header and ends with
"ArkEnv scaffolding complete. Happy coding!").
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 0c9d372a-87e3-4932-aae2-23d47334751a
📒 Files selected for processing (3)
.changeset/great-deer-check.mdpackages/cli/src/commands/init.tspackages/cli/src/lib/logger.ts
| ``` | ||
| 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! | ||
| ``` |
There was a problem hiding this comment.
Add a language identifier to the fenced code block.
Line 9 uses an unlabeled fence, which triggers markdownlint MD040.
Proposed fix
-```
+```text
1 │
2 ◇ Next steps ─────────────────────────────────────────────────────────────────╮
3 │ │
@@
11 └ ⛯ ArkEnv scaffolding complete. Happy coding!
-```
+```🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 9-9: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.changeset/great-deer-check.md around lines 9 - 21, The fenced code block
that contains the "Next steps" ASCII art is missing a language identifier which
triggers markdownlint MD040; fix this by changing the opening fence from ``` to
```text so the block is labeled as plain text (the block that starts with the
"Next steps" header and ends with "ArkEnv scaffolding complete. Happy coding!").
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This PR was opened by the [Changesets release](https://github.com/changesets/action) 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`](#945) [`63d6237`](63d6237) [@yamcodes](https://github.com/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](https://arkenv.js.org/docs/cli). - #### Improve "done" message text _[`#954`](#954) [`fe10ef4`](fe10ef4) [@yamcodes](https://github.com/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`](#948) [`1dca74c`](1dca74c) [@yamcodes](https://github.com/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`](#952) [`10cbb7d`](10cbb7d) [@yamcodes](https://github.com/yamcodes)_ The ArkEnv CLI will now pass the flags `--yes` and `--quiet` to underlying processes. This means that if you run: ```sh 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: ```sh 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) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Summary by CodeRabbit