@opengamehq/cli 0.9.9 → 0.11.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 (30) hide show
  1. package/AGENTS.md +29 -14
  2. package/CHANGELOG.md +46 -0
  3. package/README.md +20 -9
  4. package/dist/cli.mjs +151 -146
  5. package/dist/opengame-global.js +3 -3
  6. package/dist/preflight-worker.mjs +1 -1
  7. package/dist/runtime-builder.mjs +1 -1
  8. package/dist/skills/manifest.json +36 -36
  9. package/dist/skills/opengame-all-in-one/SKILL.md +4 -4
  10. package/dist/skills/opengame-all-in-one/references/opengame-api/README.md +4 -3
  11. package/dist/skills/opengame-all-in-one/references/opengame-cli/README.md +11 -8
  12. package/dist/skills/opengame-all-in-one/references/opengame-deploy/README.md +25 -12
  13. package/dist/skills/opengame-all-in-one/references/opengame-deploy/references/json-events.md +11 -10
  14. package/dist/skills/opengame-all-in-one/references/opengame-deploy/references/manifest.md +17 -11
  15. package/dist/skills/opengame-all-in-one/references/opengame-deploy/references/packaging.md +3 -2
  16. package/dist/skills/opengame-all-in-one/references/opengame-jam/README.md +23 -16
  17. package/dist/skills/opengame-all-in-one/references/opengame-performance/README.md +3 -3
  18. package/dist/skills/opengame-all-in-one/references/opengame-router/README.md +7 -5
  19. package/dist/skills/opengame-all-in-one/references/opengame-router/references/process.md +5 -2
  20. package/dist/skills/opengame-api/SKILL.md +4 -3
  21. package/dist/skills/opengame-cli/SKILL.md +11 -8
  22. package/dist/skills/opengame-deploy/SKILL.md +25 -12
  23. package/dist/skills/opengame-deploy/references/json-events.md +11 -10
  24. package/dist/skills/opengame-deploy/references/manifest.md +17 -11
  25. package/dist/skills/opengame-deploy/references/packaging.md +3 -2
  26. package/dist/skills/opengame-jam/SKILL.md +24 -17
  27. package/dist/skills/opengame-performance/SKILL.md +3 -3
  28. package/dist/skills/opengame-router/SKILL.md +7 -5
  29. package/dist/skills/opengame-router/references/process.md +5 -2
  30. package/package.json +1 -1
package/AGENTS.md CHANGED
@@ -3,12 +3,13 @@
3
3
  How a coding agent deploys a creator's game with the `opengame` command. The command and exit code tables at the end are the CLI's own help; `opengame help --json` has every flag.
4
4
 
5
5
  <!-- generated:procedure -->
6
- Deploy the creator's game to a private preview and give them its link. Review starts automatically, and the creator publishes the game on the deploy's page. Read each command's result before you run the next one.
6
+ Deploy the creator's game to a private preview and give them its link. Review starts automatically. When it passes, publish the game with `opengame publish` if the creator asked you to, or give them the deploy's page to publish it themselves. Read each command's result before you run the next one.
7
7
 
8
8
  ## Install
9
9
 
10
10
  ```bash
11
11
  npm i -g @opengamehq/cli
12
+ opengame setup
12
13
  ```
13
14
 
14
15
  Once `opengame` is installed, confirm it and read the command reference:
@@ -20,7 +21,9 @@ opengame help --json
20
21
 
21
22
  `help --json` lists every command, flag, exit code, environment variable and event, with the finding schema. Read it rather than guessing a flag.
22
23
 
23
- Install the OpenGame skills for the agent you run in, from the game folder:
24
+ `opengame setup` installs every OpenGame skill in the home folder of each coding agent it finds (Claude Code, Codex, Cursor and OpenCode), and later commands keep them current. If your session started before that, read `opengame-router/SKILL.md` in the folder it names.
25
+
26
+ To commit the skills with the game instead:
24
27
 
25
28
  ```bash
26
29
  opengame skills add .
@@ -98,7 +101,7 @@ opengame init . --title "My game" --json
98
101
  opengame init . --title "Doom but blue" --kind mod --based-on "Doom" --json
99
102
  ```
100
103
 
101
- Do not ask the creator for a description or a genre before deploying. When you know them, pass `--description` (40 characters or more) and `--genre`; when you do not, leave them out. Every field defaults to Auto: review writes the description and the genre from the game, and the creator accepts or changes them on the deploy's page, where they also enter the jam. After the deploy you can set the description yourself with `opengame details --description "..." --json`. If the file already exists, leave `init` alone and edit the file.
104
+ Do not ask the creator for a description or a genre before deploying. When you know them, pass `--description` (40 characters or more) and `--genre`; when you do not, leave them out. Every field defaults to Auto: review writes the description and the genre from the game, and the creator accepts or changes them on the deploy's page, where they also enter the jam. A title or description you pass is offered back with its casing and grammar tidied, and `opengame publish --keep-words` keeps it as written. After the deploy you can set the description yourself with `opengame details --description "..." --json`. If the file already exists, `init` fills in only the fields it leaves blank; edit the file to change the rest.
102
105
 
103
106
  For a game that already exists on OpenGame, in a new checkout, link the folder first so the deploy does not create a second game:
104
107
 
@@ -121,7 +124,7 @@ opengame deploy . --json
121
124
  | `data.deploymentUrl` | The deploy's page. Give it to the creator straight away: it shows each check and plays the preview once they pass. |
122
125
  | `data.state` | `uploading`, `queued`, `checking`, `ready`, `failed` or `expired`. |
123
126
  | `data.done` | `true` once the server has finished. |
124
- | `data.releaseId` | The release. Keep it for `submit`. |
127
+ | `data.releaseId` | The release. Keep it: `opengame publish --release` takes it. |
125
128
  | `data.previewUrl` | The private preview link, once `state` is `ready`. It can be `null` on a ready release the server will not play; the deploy's page says why. |
126
129
  | `data.gameOrigin` | The origin the published game runs at, such as `https://k3v9q2m7x4ab.opengame.gg`. Give it to the creator when the game talks to their own servers. `null` when the server sent none, or sent one this CLI cannot read. |
127
130
 
@@ -163,13 +166,18 @@ An account can begin 5 deploys in a rolling day, so fix what `opengame check` fi
163
166
 
164
167
  Review starts automatically once a deploy is ready, so you submit no release. Review is automatic: it plays the game, then passes it or returns it with findings.
165
168
 
166
- When review passes, the release waits for the creator. `opengame status --json` shows `data.review.state: "awaiting_details"` and the deploy's page in `data.review.url`. Give the creator that link. Signed in, in their own browser, they confirm the title, description and genre, enter the jam with its track and the models they used, and publish. You cannot do this for them. Before they do, you can set the words with `opengame details --title "..." --description "..." --json`.
169
+ When review passes, a game's first release waits to be published. `opengame status --json` shows `data.review.state: "awaiting_details"`, `data.review.next: "opengame publish"` and the deploy's page in `data.review.url`.
170
+
171
+ - **The creator asked you to publish it.** Run `opengame publish --json`. It confirms the title, description and genre review wrote, publishes, waits until the game is live and prints the address to share in `data.url`. Change what review wrote with `--description`, `--genre` and the other flags in `opengame publish --help`. While a new game or an update goes on OpenGame only as a jam entry, pass the jam's track and the models used with `--track` and `--models`; `opengame jams <slug> --json` lists them.
172
+ - **They did not ask.** Give them `data.review.url`. Signed in, they check the details, enter the jam and publish on that page.
173
+
174
+ To publish in one step, `opengame deploy --publish --json` stays until review passes, then publishes, and takes the same jam flags.
167
175
 
168
- An update to a game that is already live is the exception. When the token that deployed it holds `submit`, as the `opengame login` token does, and nothing is owed (its details are written and the jam is not asking), it goes live as soon as it passes review, with no step on the page. When the creator asked only for a preview of an update to a live game, deploy with a token made in their settings with `deploy` alone, set as `OPENGAME_TOKEN`, so the release waits for them.
176
+ An update to a game that is already live publishes by itself once it passes review. It keeps the live game's details, including the genre when the deploy left it to Auto, and its jam entry. The token that deployed it has to hold `submit`, as the `opengame login` token does. When the creator asked only for a preview of an update to a live game, deploy with a token made in their settings with `deploy` alone, set as `OPENGAME_TOKEN`, so the release waits for them.
169
177
 
170
- `opengame submit` cannot take the confirmation step either. The release is already in review, so the server keeps that submission and prints a `jam_answers_unused` notice: the jam answers you passed were not used.
178
+ `opengame submit` does not confirm a release that is already in review. The server keeps that submission, and the CLI prints a `jam_answers_unused` notice: the jam answers you passed were not used. Pass them to `opengame publish` once review passes.
171
179
 
172
- While Game Jam #1 runs, a new game goes on OpenGame only as a jam entry, up to 2 for each account. Mods and decomps publish outside the jam at any time and never enter it. When the jam cannot take a build, for example because the account already has 2 entries, the build is not sent to review, and the deploy's page explains why. [Enter a jam](https://docs.opengame.io/guides/jams) has the rules.
180
+ While Game Jam #1 runs, a new game or an update goes on OpenGame only as a jam entry, up to 2 for each account. Mods and decomps publish outside the jam at any time and never enter it. When the jam cannot take a build, for example because the account already has 2 entries, the build is not sent to review, and the deploy's page explains why. [Enter a jam](https://docs.opengame.io/guides/jams) has the rules.
173
181
 
174
182
  Follow the release to the end:
175
183
 
@@ -180,9 +188,14 @@ opengame status --watch --json
180
188
  | `data.review.state` | What to do |
181
189
  | --- | --- |
182
190
  | `review`, `playtesting`, `waiting` | Review is running. Watch again. |
183
- | `awaiting_details`, `needs_certification` | Give the creator `data.review.url`. Watch again once they say they have published. |
184
- | `publishing`, `published` | The game is going live. `data.submission.gameUrl` is its page. |
185
- | `returned` | Read the findings, fix the game and deploy again. The new deploy is reviewed automatically. |
191
+ | `approved` | Review passed. When `data.review.next` is `opengame publish`, do as for `awaiting_details`; otherwise watch again. |
192
+ | `awaiting_details` | Run `opengame publish --json` when the creator asked you to publish. Otherwise give them `data.review.url`, and watch again once they say they have published. |
193
+ | `needs_certification` | Give the creator `data.review.url`. Watch again once they say they have done it. |
194
+ | `publishing`, `published` | The game is going live. Once it is, `data.submission.live.url` is the address to share. |
195
+ | `returned` | Read the findings and run `data.review.next`. Usually that means fix the game and deploy again, and the new deploy is reviewed automatically. A jam entry returned for a fault on our side gets `opengame submit --release <id>` instead: the game needs no change, and the command names any jam answer it still needs. |
196
+ | `blocked` | Review refused the game. Give the creator `data.review.message`. |
197
+ | `withdrawn` | The creator withdrew this submission. Nothing more happens to it unless they ask you to enter it again. |
198
+ | `superseded` | Another submission took its place, and `data.submission.replacedBy` names it. Run `opengame status --json` again to follow that one. |
186
199
 
187
200
  ## What a game may do
188
201
 
@@ -222,7 +235,7 @@ Play the private preview before you tell the creator the game works.
222
235
  <!-- generated:commands -->
223
236
  | Command | What it does |
224
237
  | --- | --- |
225
- | `opengame init [dir] [options]` | Create opengame.json for an existing game. Every field defaults to Auto. Leave a field out, blank or "auto" and review writes it from your game; you accept or change it on the deploy's page. A person at a terminal is asked the game's name and nothing else, and Enter takes Auto. When opengame.json is already there, fill in the fields it leaves blank and keep the rest. |
238
+ | `opengame init [dir] [options]` | Create opengame.json for an existing game. Every field defaults to Auto. Leave a field out, blank or "auto" and review writes it from your game; you accept or change it on the deploy's page, or with opengame publish. A person at a terminal is asked the game's name and nothing else, and Enter takes Auto. When opengame.json is already there, fill in the fields it leaves blank and keep the rest. |
226
239
  | `opengame check [dir] [options]` | Find local build and asset problems before uploading. |
227
240
  | `opengame dev [dir] [options]` | Serve a local export with game-runtime headers. Under a contract that adds the SDK, pages also get the host runtime and SDK, as they do when hosted. If the contract supports opting out, sdk.inject: false leaves out the SDK. |
228
241
  | `opengame login [options]` | Sign in through your browser. |
@@ -230,6 +243,7 @@ Play the private preview before you tell the creator the game works.
230
243
  | `opengame status [dir] [options]` | Show the most recent deploy for this folder, with its findings. Finishes saving its declared achievements if the deploy could not. Removing an achievement from opengame.json does not switch it off. To retire one, run opengame achievements retire <id> and take it out of opengame.json too, since a deploy that still declares it turns it back on. Unlocks are never deleted. |
231
244
  | `opengame deployments [dir] [options]` | List the linked game's deploys, newest first: status, when, size, who started each one, why any stopped, and each one's page or preview. |
232
245
  | `opengame open [dir] [options]` | Open the linked game's private page in your browser. |
246
+ | `opengame publish [dir] [options]` | Publish the linked game's release that passed review, as Confirm and publish does on its deploy's page, then follow it until it is live and print the address to share. Each detail left out is what that page would have sent: the game's words and genre, and review's choice for anything the deploy left to Auto. An update of a game that is already live publishes with no command once it passes review, so this is for a first publish, or a release that waits for a detail only you can give, such as the jam's track. Needs a token with submit; opengame login has it. |
233
247
  | `opengame submit [dir] [options]` | Send one release to review that was not sent by itself. A deploy goes to review by itself once it is ready, and the jam is entered on its deploy's page, so this is only for a build that was not sent: a QA game (--qa), a build deployed before reviews started by themselves, or one whose deploy token could not replace a jam entry. A release already in review keeps its submission, and jam answers given here are not used. A person who names no jam answer is given the deploy's page, and nothing is sent. |
234
248
  | `opengame jams [slug] [options]` | List open jams, or show one jam's tracks and flags. |
235
249
  | `opengame jam <withdraw\|reenter> [options]` | Withdraw the linked game's jam entry, freeing its place, or put a withdrawn one back while the jam is open, as your jam entries page does. Needs a token with submit; opengame login has it. |
@@ -239,7 +253,7 @@ Play the private preview before you tell the creator the game works.
239
253
  | `opengame restore [dir] [options]` | Put a game you unpublished back on the gallery, serving the version it was on, as Put it back does on Your games. Refused for a game we took down, one with an open report or a hold, and one under a copyright notice. Needs a token with read or deploy, and submit; opengame login has all three. |
240
254
  | `opengame delete [dir] [options]` | Delete the linked game for good, as Delete for good does on its page: it comes off the gallery, stops being served and cannot be put back. You type its title to confirm. Refused while it is under a legal hold, with a reviewer, or in a jam being scored. Only the opengame login token can do this, not a token made in settings. |
241
255
  | `opengame details [dir] [options]` | Print the linked game's title, tagline and description as the website shows them, or change any of them, as the Details tab on its page does. A field you leave out stays as it is. On a published game players see the change at once. Printing needs a token with read or deploy, and saving needs submit too; opengame login has all three. |
242
- | `opengame achievements [retire <id>] [options]` | List the linked game's achievements, active and retired, or retire one, as the achievements step on the website does. Players keep what they unlocked, and the game can no longer award a retired one. Retiring needs a token with deploy and submit; opengame login has them. |
256
+ | `opengame achievements [retire <id>] [options]` | List the linked game's achievements, active and retired, or retire one. Players keep what they unlocked, and the game can no longer award a retired one. Retiring needs a token with deploy and submit; opengame login has them. |
243
257
  | `opengame games [options]` | List your games and their latest deploy. |
244
258
  | `opengame link [dir] [options]` | Connect this folder to an existing game. |
245
259
  | `opengame pull [dir] [options]` | Bring website metadata into this folder. |
@@ -250,7 +264,8 @@ Play the private preview before you tell the creator the game works.
250
264
  | `opengame logout [options]` | Revoke this device's token and remove it locally. |
251
265
  | `opengame limits [options]` | Show bundle limits and your remaining account allowance. |
252
266
  | `opengame vendor [dir] [options]` | Create a separate export with dependencies downloaded at their exact versions, rewritten and hashed. |
253
- | `opengame skills add\|list [dir] [options]` | Install the OpenGame skills for your coding agent. |
267
+ | `opengame setup [options]` | Install the OpenGame skills for your coding agents and keep them updated with the CLI. Other commands also do it on first run and after an update. |
268
+ | `opengame skills add\|list [dir] [options]` | Install the OpenGame skills into one project, to commit them with it. |
254
269
  | `opengame upgrade [options]` | Install the current CLI, or print the line that does. |
255
270
  | `opengame version [options]` | Print the CLI version. |
256
271
 
package/CHANGELOG.md CHANGED
@@ -1,5 +1,51 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.11.0
4
+
5
+ - `opengame setup` gives your coding agents the OpenGame skills: every skill this CLI carries,
6
+ in each agent's own folder in your home directory (`~/.claude/skills`, or under
7
+ `$CLAUDE_CONFIG_DIR`; `~/.agents/skills` for Codex; `~/.cursor/skills`;
8
+ `~/.config/opencode/skills`), for the agents installed on the machine or the ones `--agent`
9
+ names. Run it once after installing.
10
+ - Any other command does the same the first time it runs, and again after the CLI is updated,
11
+ so the skills stay as current as the CLI. A notice says when it happens. Skills you edited,
12
+ folders the CLI did not write, and skills you removed are left as they are.
13
+ - `opengame check`, `dev` and `deploy` bring older copies from `opengame skills add` in the
14
+ project's agent folders up to this CLI's, one agent's folder at a time.
15
+ - `opengame setup --no-skills` stops the install and the updates for good, and
16
+ `OPENGAME_SKILLS_AUTO=0` for one run. In CI they never run.
17
+ - The staging folder an install uses beside an agent's folder must be a real folder, never a
18
+ link, and is tidied only where an install writes.
19
+ - Carries the skills from `@opengamehq/skills` 1.7.0, which install the CLI with `opengame setup`.
20
+ - `~/.config/opengame/skills.json` records each agent's own CLI version and skills, so
21
+ `opengame setup --agent codex` after an update leaves Claude Code to be refreshed by the next
22
+ command rather than marking it current. A file from before is read as each agent's own.
23
+ - An `opengame setup --no-skills` saved while another command was installing skills stands:
24
+ every change to that file is read and written under a lock, from the file as it is then.
25
+ - `opengame` with no command lists `publish` among the first five, in place of `submit`, which
26
+ is now only for a release that was not sent to review by itself. `achievements` no longer
27
+ says the website has a retire control; `opengame achievements retire` is the way.
28
+ - `opengame dev`'s SDK names the radio by its real module in its error hints, and says what a
29
+ `cancelled` means: the call was stopped, as when the player chose Keep playing on a link.
30
+
31
+ ## 0.10.0
32
+
33
+ - `opengame publish` publishes a release that passed review, as Confirm and publish does on
34
+ the deploy's page and through the same confirmation: the details review wrote, or the ones
35
+ given as flags (`--description`, `--genre`, `--subgenre`, `--tagline`, `--controller`,
36
+ `--keep-words`), and for a jam entry its track, models and sponsor tracks
37
+ (`--track`, `--models`, `--sponsor`, `--sponsor-email`), or `--no-jam` for the gallery. It
38
+ follows the publication until the game is live and prints the address to share. `--wait`
39
+ waits for review first. Needs a token with `submit`; `opengame login` has it.
40
+ - `opengame deploy --publish` waits for the checks and review and publishes the release the
41
+ moment review passes, first publish included, taking the same jam flags.
42
+ - An update of a game that is already live publishes by itself once it passes review, keeping
43
+ the live game's details and jam entry, so `opengame status` no longer sends you to the
44
+ deploy's page for it. For a release that waits, `next` is now `opengame publish`.
45
+ - A deploy step past its usual time says how long it has run ("18 s so far"), not that it is
46
+ taking longer than usual.
47
+ - Carries the skills from `@opengamehq/skills` 1.6.0, which publish with `opengame publish`.
48
+
3
49
  ## 0.9.9
4
50
 
5
51
  - Carries the skills from `@opengamehq/skills` 1.5.0: what OG Snipers, Last Contact and OG Hero
package/README.md CHANGED
@@ -8,6 +8,7 @@ command checks a game folder, uploads it and gives you a private preview to play
8
8
  <!-- install:cli -->
9
9
  ```bash
10
10
  npm i -g @opengamehq/cli
11
+ opengame setup
11
12
  ```
12
13
  <!-- /install -->
13
14
 
@@ -40,10 +41,11 @@ opengame deploy .
40
41
  ```
41
42
 
42
43
  `init` writes `opengame.json`, the manifest with your game's title and build. It asks
43
- you one thing, the game's name, and you write the description, choose the genre and
44
- enter the jam on the deployment page afterwards. Your agent can write the description
45
- and genre with `opengame details`; entering the jam and publishing are yours. `check` runs the same checks the upload will, on your machine. `deploy` builds,
46
- checks and uploads a release, then prints its deployment page:
44
+ you one thing, the game's name, and leaves every other field on Auto: review writes the
45
+ description and chooses the genre from the game, and you accept or change them on the
46
+ deployment page. Your agent can set the title, tagline and description with
47
+ `opengame details`. `check` runs the same checks the upload will, on your machine.
48
+ `deploy` builds, checks and uploads a release, then prints its deployment page:
47
49
 
48
50
  ```
49
51
  Uploaded. The checks run on our side, so you can close this terminal.
@@ -55,6 +57,11 @@ Or follow them here with opengame status --watch.
55
57
  The private preview plays on that page once the checks pass, and the release goes to
56
58
  review by itself. Add `--wait` to stay in the terminal until the checks finish.
57
59
 
60
+ When review passes, publish the game on that page, where you also enter the jam, or with
61
+ `opengame publish`. `opengame deploy --publish` deploys, waits for review and publishes in
62
+ one command. An update of a game that is already live publishes by itself once it passes
63
+ review.
64
+
58
65
  ## Scripts and agents
59
66
 
60
67
  Every command takes `--json` and prints one result object. For `deploy`:
@@ -76,15 +83,17 @@ A failure prints `"type": "error"` with `ok: false`, a `code` such as `not_launc
76
83
  `message` and the process exits with a non-zero code. `opengame help --json`
77
84
  lists every command, flag and exit code. `--jsonl` streams progress events.
78
85
 
79
- `opengame skills add .` installs the OpenGame skills for Claude Code, Codex, Cursor or
80
- OpenCode, so a coding agent can do all of the above for you.
86
+ `opengame setup` installs the OpenGame skills for Claude Code, Codex, Cursor and OpenCode
87
+ in your home folder, so a coding agent can do all of the above for you, and the CLI keeps
88
+ them current as it updates. `opengame setup --no-skills` turns that off.
89
+ `opengame skills add .` installs them into one project instead, to commit with it.
81
90
 
82
91
  ## Commands
83
92
 
84
93
  <!-- generated:commands -->
85
94
  | Command | What it does |
86
95
  | --- | --- |
87
- | `opengame init [dir] [options]` | Create opengame.json for an existing game. Every field defaults to Auto. Leave a field out, blank or "auto" and review writes it from your game; you accept or change it on the deploy's page. A person at a terminal is asked the game's name and nothing else, and Enter takes Auto. When opengame.json is already there, fill in the fields it leaves blank and keep the rest. |
96
+ | `opengame init [dir] [options]` | Create opengame.json for an existing game. Every field defaults to Auto. Leave a field out, blank or "auto" and review writes it from your game; you accept or change it on the deploy's page, or with opengame publish. A person at a terminal is asked the game's name and nothing else, and Enter takes Auto. When opengame.json is already there, fill in the fields it leaves blank and keep the rest. |
88
97
  | `opengame check [dir] [options]` | Find local build and asset problems before uploading. |
89
98
  | `opengame dev [dir] [options]` | Serve a local export with game-runtime headers. Under a contract that adds the SDK, pages also get the host runtime and SDK, as they do when hosted. If the contract supports opting out, sdk.inject: false leaves out the SDK. |
90
99
  | `opengame login [options]` | Sign in through your browser. |
@@ -92,6 +101,7 @@ OpenCode, so a coding agent can do all of the above for you.
92
101
  | `opengame status [dir] [options]` | Show the most recent deploy for this folder, with its findings. Finishes saving its declared achievements if the deploy could not. Removing an achievement from opengame.json does not switch it off. To retire one, run opengame achievements retire <id> and take it out of opengame.json too, since a deploy that still declares it turns it back on. Unlocks are never deleted. |
93
102
  | `opengame deployments [dir] [options]` | List the linked game's deploys, newest first: status, when, size, who started each one, why any stopped, and each one's page or preview. |
94
103
  | `opengame open [dir] [options]` | Open the linked game's private page in your browser. |
104
+ | `opengame publish [dir] [options]` | Publish the linked game's release that passed review, as Confirm and publish does on its deploy's page, then follow it until it is live and print the address to share. Each detail left out is what that page would have sent: the game's words and genre, and review's choice for anything the deploy left to Auto. An update of a game that is already live publishes with no command once it passes review, so this is for a first publish, or a release that waits for a detail only you can give, such as the jam's track. Needs a token with submit; opengame login has it. |
95
105
  | `opengame submit [dir] [options]` | Send one release to review that was not sent by itself. A deploy goes to review by itself once it is ready, and the jam is entered on its deploy's page, so this is only for a build that was not sent: a QA game (--qa), a build deployed before reviews started by themselves, or one whose deploy token could not replace a jam entry. A release already in review keeps its submission, and jam answers given here are not used. A person who names no jam answer is given the deploy's page, and nothing is sent. |
96
106
  | `opengame jams [slug] [options]` | List open jams, or show one jam's tracks and flags. |
97
107
  | `opengame jam <withdraw\|reenter> [options]` | Withdraw the linked game's jam entry, freeing its place, or put a withdrawn one back while the jam is open, as your jam entries page does. Needs a token with submit; opengame login has it. |
@@ -101,7 +111,7 @@ OpenCode, so a coding agent can do all of the above for you.
101
111
  | `opengame restore [dir] [options]` | Put a game you unpublished back on the gallery, serving the version it was on, as Put it back does on Your games. Refused for a game we took down, one with an open report or a hold, and one under a copyright notice. Needs a token with read or deploy, and submit; opengame login has all three. |
102
112
  | `opengame delete [dir] [options]` | Delete the linked game for good, as Delete for good does on its page: it comes off the gallery, stops being served and cannot be put back. You type its title to confirm. Refused while it is under a legal hold, with a reviewer, or in a jam being scored. Only the opengame login token can do this, not a token made in settings. |
103
113
  | `opengame details [dir] [options]` | Print the linked game's title, tagline and description as the website shows them, or change any of them, as the Details tab on its page does. A field you leave out stays as it is. On a published game players see the change at once. Printing needs a token with read or deploy, and saving needs submit too; opengame login has all three. |
104
- | `opengame achievements [retire <id>] [options]` | List the linked game's achievements, active and retired, or retire one, as the achievements step on the website does. Players keep what they unlocked, and the game can no longer award a retired one. Retiring needs a token with deploy and submit; opengame login has them. |
114
+ | `opengame achievements [retire <id>] [options]` | List the linked game's achievements, active and retired, or retire one. Players keep what they unlocked, and the game can no longer award a retired one. Retiring needs a token with deploy and submit; opengame login has them. |
105
115
  | `opengame games [options]` | List your games and their latest deploy. |
106
116
  | `opengame link [dir] [options]` | Connect this folder to an existing game. |
107
117
  | `opengame pull [dir] [options]` | Bring website metadata into this folder. |
@@ -112,7 +122,8 @@ OpenCode, so a coding agent can do all of the above for you.
112
122
  | `opengame logout [options]` | Revoke this device's token and remove it locally. |
113
123
  | `opengame limits [options]` | Show bundle limits and your remaining account allowance. |
114
124
  | `opengame vendor [dir] [options]` | Create a separate export with dependencies downloaded at their exact versions, rewritten and hashed. |
115
- | `opengame skills add\|list [dir] [options]` | Install the OpenGame skills for your coding agent. |
125
+ | `opengame setup [options]` | Install the OpenGame skills for your coding agents and keep them updated with the CLI. Other commands also do it on first run and after an update. |
126
+ | `opengame skills add\|list [dir] [options]` | Install the OpenGame skills into one project, to commit them with it. |
116
127
  | `opengame upgrade [options]` | Install the current CLI, or print the line that does. |
117
128
  | `opengame version [options]` | Print the CLI version. |
118
129