Skill Claude Code
Commit changes across the LiteStack meta-repo and its submodules. Use when the user asks to commit or push from the LiteStack root. It commits inside each changed submodule first, then records the updated submodule pointers in the meta-repo, and pushes according to the operating mode (template vs derived).
Skill Claude Code
Order a feature that needs changes in both backend/ and frontend/ — e.g. a new GraphQL field shown in the UI. Runs the backend first, regenerates the frontend types, then builds the UI.
Skill Claude Code
Create a new product (backend + frontend pair) from the LiteStack templates — a meta-repo with submodules in DERIVED mode, repointed at the team's own repos, renamed, installed and running. Use when the user wants to start a new project or app from LiteStack.
Skill Claude Code
Write a session retrospective to docs/retro/ — what went wrong, its root cause, and the check or rule that stops it happening again. Use at the end of a session where a command failed, work was redone or an assumption proved wrong, or when the user asks for a retro or lessons learned.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: