STAR: Command for Claude Code

Drive the workflow toward a goal

The user has typed star-auto — this file is what that invocation runs. Typing it is the auto grant of conventions §10.7: while this run pursues its goal, the skill each next action names may be started without further naming, the seven explicit-only ones included, and a prepared STOP-line command may be launched instead of handed back. At involve=low, that same explicit grant also covers the executor chain's routine local implementation, mechanical review fixes, and Git lifecycle described below; a started run otherwise behaves exactly as if the user had typed its name.

Invocation shape: star-auto <GOAL> [stop=<STOP-LINE>] [involve=<level>].

Parse the invocation

• Strip involve=<level> first, taken from outside the stop text — before stop=, or as the invocation's final token; the same words inside the stop line are stop-line text, not the token (conventions §7.7). When nothing sets a level — no token, no INVOLVE in .env — this run resolves to low, not medium: an autonomous run takes the marked recommendation on its own judgment calls and logs each (§7.8). At low, the invocation itself pre-approves the executor's recommended plan, explicit-path staging and commits, execution-branch or worktree creation, behavior-preserving review fixes that delete nothing, a clean reviewed squash merge, and removal of a worktree only after its durable artifacts have moved out and git status --porcelain is empty. Those operations run without an authorization question and are logged. Review fixes that require deletion are skipped and routed rather than guessed. The merged execution branch is retained without asking, so unattended cleanup never needs a forced delete. This exception is carried to the executor and code reviewer as the internal auto=unattended token; it is not part of the user-facing invocation shape.
• Then strip stop=: everything from that token to the end of what remains is the stop line, natural language in the user's own words — stop=any single training over 4 hours, or any paid API call, stop=用卡超过 2 张就停 (either language, or both at once). Given, it is the line this run must not cross: before launching a prepared command, state its expected cost and judge it against each condition — a command that crosses the line, or that cannot be judged against it, is printed and handed back exactly as §2 says. Absent, the run is uncapped: prepared STOP-line commands launch autonomously, the goal owning the run (§2's one exception). Either way every launch is logged in the decisions record with its stated cost. Apart from the clean worktree removal above, neither the grant nor any stop line covers deletion, overwrite, sudo, system or driver installation, history rewriting, forced Git, push, discarding unmerged work, or resolving a merge conflict — those stop and report instead of being guessed through.
• What remains is the goal. No goal — ask for one; never infer a goal from the repository.