@duyquangnvx/create-agent-cli 0.19.0 → 0.21.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/CHANGELOG.md +26 -0
  2. package/dist/bin.js +1037 -983
  3. package/package.json +2 -2
  4. package/template/skills/{{binName}}/SKILL.md +5 -13
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@duyquangnvx/create-agent-cli",
3
- "version": "0.19.0",
3
+ "version": "0.21.0",
4
4
  "description": "Creates a new Agent CLI repository wired to @duyquangnvx/agent-cli.",
5
5
  "type": "module",
6
6
  "engines": {
@@ -21,7 +21,7 @@
21
21
  "access": "public"
22
22
  },
23
23
  "devDependencies": {
24
- "@duyquangnvx/agent-cli": "0.19.0",
24
+ "@duyquangnvx/agent-cli": "0.21.0",
25
25
  "tsdown": "0.23.0",
26
26
  "zod": "4.6.7"
27
27
  },
package/template/skills/{{binName}}/SKILL.md CHANGED
@@ -47,18 +47,10 @@ Pass `--json` whenever you parse the output: stdout then holds only the data. A
47
47
 
48
48
  ## Recovering from errors
49
49
 
50
- Errors go to stderr and end with a `hint:` line, then a `run:` line for each command to run next, in order. Under `--json`, every stderr line is one JSON object: `{"progress":"..."}` or `{"notice":"..."}` while it runs, then `{ errors: [{ code, message, hint, next }] }` as the last line, `next` holding those commands when there are any. Match the first row that fits:
50
+ Errors go to stderr and end with a `hint:` line, then a `run:` line for each command to run next, in order. Under `--json`, every stderr line is one JSON object: `{"progress":"..."}` or `{"notice":"..."}` while it runs, then `{ errors: [{ code, message, hint, next }] }` as the last line, `next` holding those commands when there are any. Do what the hint says, except for a code below:
51
51
 
52
- | Code or exit | What to do |
52
+ | Code | What to do |
53
53
  |---|---|
54
- | `OUTPUT_EXISTS` | The run would overwrite a file. Ask the user before adding `--force`. |
55
- | `NOT_CONFIRMED` | The run costs money. Tell the user the cost from the message; add `--yes` only once they approve it. |
56
- | `LANGUAGE_UNSUPPORTED` | The greetings service lacks that language. Run the Next step's English card, or ask the user for another language. |
57
- | exit 1 | You called it wrong. Fix what the message and hint point at, then run it again. |
58
- | exit 2 | Something on this machine needs a person. Tell the user what the hint says and ask them to fix it. |
59
- | exit 3 | The source it talks to is broken. Tell the user; running it again won't help. |
60
- | exit 75 | Nobody needs to act. Wait, then run it again, as the hint says. |
61
- | exit 70, `INTERNAL` | A bug in {{binName}}. Run it once more with `{{debugVariable}}=1` for the stack trace, then give the user stderr verbatim. |
62
- | exit 130 or 143 | It was interrupted. Run it again only if the user still wants it. |
63
-
64
- <!-- Add a row above the exit rows for each CliError code {{binName}} throws, saying what to do about it. -->
54
+ | `LANGUAGE_UNSUPPORTED` | The user asked for that language. Ask whether an English card will do before running the Next step. |
55
+
56
+ <!-- Add a row for each code {{binName}} throws whose right move goes beyond its hint. A guardrail on a flag goes in the workflow step that passes it instead. -->