For developers who want to continually save their changes for version control purposes, doing this through the UI can be cumbersome. Beyond just "save", I think many of the commands in CBT could also have complementary WPCLI commands, like making a variation or exporting the theme.

"Save" Example

I've created a very crude, messy example of what it could look like to have a "save" command like this

wp cbt save or wp cbt save --saveTemplates et cetera

that a developer could run at any time to push their changes to their local theme or automate somehow.

This is not opened as a PR because it's not meant to be good code! It's just a janky working demo to see if the idea felt helpful in practice. A real PR would need to have some sort of abstraction layer and better loading of the class, right now I'm just duplicating code from the rest API endpoints.

https://github.com/bacoords/create-block-theme/tree/add/cli-export-command