@duyquangnvx/create-agent-cli 0.22.0 → 0.24.0

package/CHANGELOG.md

@@ -4,6 +4,43 @@ What changed in each release of `@duyquangnvx/agent-cli` (the Runtime) and `@duy
 
 ## Unreleased
 
+## v0.24.0 (2026-11-05)
+
+### Added
+
+- A Global install of a CLI with several Commands has the Built-in `setup`, run as `npx -y <package>@latest setup` before the CLI is on the machine: it installs the latest release, copies the skill to `~/.claude/skills/<name>` and `~/.agents/skills/<name>`, and names the CLI docs. `setupLineOf` builds that line. It fails with the new `NOT_ON_PATH` (exit 2) when the global bin folder is off this shell's `PATH`.
+- The Scaffolder's `bin` checks `engines.node` before it imports anything, and exits 2 naming the version needed. A CLI that exists already gets it by copying the template's `src/bin.ts`.
+- `defineCli({ docs: "docs/cli" })` declares the CLI docs, a folder of pages shipped in the package, and `--version` prints `docs <path>` naming it, also when run from source.
+
+### Changed
+
+- **Breaking:** `defineCli`'s `skill` is `{ folder, agents? }`, in place of `{ source }`, `{ add }` and `{ packaged }`: every skill ships in the package. It throws on a skill on a single-Command CLI, and on `agents` on a Global install.
+- **Breaking:** `update` makes the home Skill copies match the release it leaves installed, and its `--json` gains `skill`.
+- **Breaking:** on a Global install, `doctor`'s `install` row fix is the `setup` line, and its `skill` row looks under home only and reports a missing or stamped copy as an advisory problem whose fix is `<run-as> setup`. A CLI declaring no skill has that row skipped.
+- **Breaking:** the Scaffolder always declares a skill, lists `skills` in `files`, refuses a name a skill cannot have, and opens a Global install's README with the sentence to paste.
+- **Breaking:** the Scaffolder writes one kind of skill: a trigger with the description, the install line and a pointer to the `docs` line, stating no version. Workflows, the Recovering from errors table and the setup page move to a new `docs/cli/` folder, which `files` lists. `scripts/release.ts` names `skill` and `skillHub` together when there is a Hub and neither otherwise, on `@duyquangnvx/release` 0.9.0. Move a CLI's own skill to this shape: its `metadata.version` goes, and everything that changes with a release moves to CLI docs.
+- **Breaking:** `doctor`'s `skill` row no longer compares versions. It reports whether a copy is there; a copy stating `metadata.version` gets `<run-as> setup`, or `<run-as> skill install` for a copy under the project. Under `--json` the row no longer carries `skill: { copy, copyVersion, packageVersion, home }`, and a copy under home is named in its message.
+- **Breaking:** `skill install` always makes the copy match the package, and `--force` is gone: the project commits the copy, so git shows the change.
+
+### Removed
+
+- **Breaking:** the Scaffolder's `--skill-hub-git`, `--skill-hub-api` and `--skill-add`. A release that still wants a Skill Hub names `skill` and `skillHub` in `scripts/release.ts`.
+- **Breaking:** `update`'s `next`, with the lines that brought Skill copies to a version.
+- A Packaged skill's Notice before each Command, and the hint on `UNKNOWN_OPTION`, `UNKNOWN_COMMAND` and `INVALID_INPUT` naming a Skill copy of another version.
+
+### Upgrade from v0.23.0
+
+- Replace `skill: { source }`, `{ add }` or `{ packaged }` with `skill: { folder: "skills/<name>" }`, and on a Global install drop `agents`.
+- List `skills` in `package.json` `files`.
+- On a Global install, open the README with the sentence to paste, give the `setup` line in the skill and `docs/cli/setup.md`, and leave the skill's Hub install line out of them. `scripts/release.ts` may keep `skillHub`.
+- A user's Skill copy from a Skill Hub is replaced by their next `setup` or `update`.
+
+## v0.23.0 (2026-11-03)
+
+### Added
+
+- A Global install of a CLI with several Commands runs a Release check: at most once a day a run asks the Install registry, in a detached process, for the latest release, and later runs give the Notice ``<cli> X.Y.Z is out, this is A.B.C; run `<cli> update` `` while the CLI is behind. No run waits on it. `CI`, or `<NAME>_NO_RELEASE_CHECK=1` for one CLI, turns it off; it keeps its answer in `$XDG_CACHE_HOME/<name>/release-check.json`, by default under `~/.cache`.
+
 ## v0.22.0 (2026-11-02)
 
 ### Added

package/README.md

@@ -3,9 +3,9 @@
 Creates a new Agent CLI repository already wired to [`@duyquangnvx/agent-cli`](https://www.npmjs.com/package/@duyquangnvx/agent-cli):
 
 ```sh
-pnpm create @duyquangnvx/agent-cli <name> --description "One line saying what it does" --skill-hub-git https://github.com/<owner>/skills.git
+pnpm create @duyquangnvx/agent-cli <name> --description "One line saying what it does"
 ```
 
-The new repository has an Error table, a port, two example Commands (one writing a file at a cost) and their test, a bundled build that stamps the commit and build time into `--version`, CI, a release script, a CHANGELOG, an `AGENTS.md` whose Agents section points Coding agents at the Runtime's docs in `node_modules`, and a skeleton skill for the new CLI whose setup reference installs, checks and updates it, so a user installs the skill first and lets their agent do the rest. `--skill-hub-git` names the git Skill Hub each release commits that skill to and agents install it from, and `--skill-hub-api` with `--skill-add` an API Skill Hub and the whole line that installs the skill from it; `--dependency` instead starts a CLI each project pins as a devDependency, run as `npx -q --no-install <name>`, whose skill ships inside the package for its `skill install` to copy into the project. Pass `--dry-run` to see what it would write.
+The new repository has an Error table, a port, two example Commands (one writing a file at a cost) and their test, a bundled build that stamps the commit and build time into `--version`, CI, a release script, a CHANGELOG, an `AGENTS.md` whose Agents section points Coding agents at the Runtime's docs in `node_modules`, a thin skill for the new CLI, and the CLI docs it points at in `docs/cli/`, so a user pastes one sentence to their agent, whose `setup` installs the CLI and the skill, and a release moves one thing. `--dependency` instead starts a CLI each project pins as a devDependency, run as `npx -q --no-install <name>`, whose `skill install` copies the skill into the project. Pass `--dry-run` to see what it would write.
 
 See the [repository](https://github.com/duyquangnvx/cli-for-agent) for an overview and the [Runtime's docs](https://github.com/duyquangnvx/cli-for-agent/blob/main/packages/agent-cli/docs/README.md) for how to build on it.