You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/product/command-spec.md
+83Lines changed: 83 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,7 @@ This file is authoritative for command group scope during beta.
10
10
11
11
The beta package includes these command groups:
12
12
13
+
-`agent`
13
14
-`auth`
14
15
-`project` (includes `project env` subgroup)
15
16
-`git`
@@ -373,6 +374,83 @@ prisma-cli --version --json
373
374
374
375
`prisma-cli version` is the richer environment report; `prisma-cli --version` is the terse one-liner. Both report the same `cli.version`. Use the flag for quick checks, the subcommand for support tickets and bug reports.
- has the same flags and behavior as `agent install`
419
+
- reruns the detected package-manager runner with `skills@latest add prisma/skills ...` instead of `skills update`, so it refreshes only Prisma's skills and works for project-scoped installs
## `<runner> @prisma/cli@latest agent status --global`
430
+
431
+
Purpose:
432
+
433
+
- show whether Prisma skills are installed for the current project or globally
434
+
435
+
Behavior:
436
+
437
+
- resolves the Compute config directory before checking project skills, so running from an app subdirectory still checks the project root
438
+
- runs `skills@latest list --json` through the detected package runner and reports installed Prisma skills from the skills CLI by default
439
+
- accepts `--global` to run `skills@latest list -g --json` and report globally installed Prisma skills instead
440
+
- filters the list to Prisma skills and includes each skill's name, path, scope, and agent targets in JSON output
441
+
- for project status, falls back to whether `skills-lock.json` references `prisma/skills` when the skills CLI list command fails
442
+
- for global status, reports the Skills CLI list failure instead of falling back to project-local state
443
+
- reports whether the project has dismissed the interactive agent setup prompt
444
+
- does not require authentication
445
+
446
+
Examples:
447
+
448
+
```bash
449
+
npx -y @prisma/cli@latest agent status
450
+
pnpm dlx @prisma/cli@latest agent status --json
451
+
pnpm dlx @prisma/cli@latest agent status --global
452
+
```
453
+
376
454
## `prisma-cli auth login`
377
455
378
456
Purpose:
@@ -386,6 +464,9 @@ Behavior:
386
464
- resolves active workspace when required
387
465
- confirms successful browser authentication and directs the user back to the terminal
388
466
- returns the current auth state after login
467
+
- in human output, when run from a project directory that does not already have Prisma skills and has not dismissed the setup prompt, suggests the detected package-runner command, such as `pnpm dlx @prisma/cli@latest agent install`
468
+
- does not install skills during auth; auth is not project-scoped and must not mutate the project
469
+
- does not show the agent setup tip in `--json`, `--quiet`, CI, non-TTY output, or directories that do not look like projects
389
470
390
471
Examples:
391
472
@@ -1066,6 +1147,8 @@ Behavior:
1066
1147
- maps user-facing framework names to deploy build strategies
1067
1148
- does not accept `--build-command` or `--output-directory`; custom build settings live in the `build` block of `prisma.compute.ts`
1068
1149
- deploys arbitrary framework output with `framework: "custom"` when the config provides a built output directory and entrypoint; `build.command` is optional for prebuilt artifacts
1150
+
- in interactive human deploys, prompts once to install the Prisma Compute skill for the project when `prisma-compute` is missing; accepting installs `prisma-compute` from `prisma/skills` from the project directory, equivalent to the detected package-runner command such as `pnpm dlx @prisma/cli@latest agent install --skill prisma-compute`; declining records the prompt as dismissed in local CLI state
1151
+
- does not prompt for agent setup in `--json`, `--quiet`, CI, `--no-interactive`, or `--yes`
1069
1152
- uses `src/index.ts` as the Hono deploy entrypoint when the app has no `package.json#main` or `package.json#module` and that file exists
1070
1153
- supports vanilla Bun apps with `--framework bun` using `package.json#main` or `package.json#module`, or with `--entry <path>`
1071
1154
- treats `--entry <path>` without `--framework` as a Bun app deploy
0 commit comments