@coderook/cli 0.31.12 → 0.32.0

package/skills/coderook/SKILL.md

@@ -81,6 +81,30 @@ cbx submit --track spike -m "…"
 Switching says where the next save goes and nothing else — no files move.
 Run `cbx get` afterwards to bring that line's files in.
 
+## A history on this machine
+
+A folder with a `.cbx/` folder in it keeps its own history, and there
+`status`, `diff`, `log`, `switch`, `merge`, `push` and `pull` work on that
+history instead of the account. Check with `cbx status`: it names the line and
+the last local save.
+
+```bash
+cbx init                       # start one (only when asked to)
+cbx save -m "…"                # record the folder as it is
+cbx log                        # saves on this line
+cbx switch -c spike            # start a line here; no files change
+cbx merge spike                # bring that line's work in
+cbx restore path --from main~1 # put a file back from an earlier save
+cbx push                       # send new saves to CodeRook
+cbx pull                       # bring CodeRook's saves in, merging if both moved
+```
+
+A merge that stops on conflicts leaves markers in the files and waits. Show
+the person the conflicts (`cbx status`) and let them decide; `cbx save`
+finishes the merge once the markers are gone. Do not pass `--force` to
+`restore`, `switch`, `save` or `pull` unless the person has said to throw away
+the changes it names, and do not run `cbx merge --cancel` unless they asked.
+
 ## Versions, and going back
 
 Every save is a commit. A commit becomes a *version* — the thing the public
@@ -115,6 +139,23 @@ cbx visibility private         # back to the people invited
 exactly that.** `--yes` skips the question the command would otherwise ask
 them, so only pass it once they have answered it. Going private is always safe.
 
+## Serving a project as a website
+
+```bash
+cbx pages                  # is the site on, its address, what it serves
+cbx pages auto             # find the build in what was published, and offer to serve it
+cbx pages on --folder dist # serve a folder of the published version
+cbx pages off              # stop serving it
+```
+
+**Never turn Pages on (`auto` or `on`) unless the person has asked for their
+project to be served as a site.** It runs their code in strangers' browsers
+under the project's name. Pass `--yes` only once they have said yes. Only
+published versions are served and the project must be public. When `auto`
+finds a build left out by the ignore rules it offers a `.gitignore` line and
+lists the next steps; it never saves or publishes — ask before doing those.
+Turning Pages off is always safe.
+
 ## When two saves collide
 
 If somebody saved while this folder was behind, the second save becomes a merge