STAR: Command for Claude Code

Drive the workflow toward a goal

Use this procedure when the user requests star-auto with a stated goal. Within that request, conventions §10.7 covers starting the skills needed for the goal, including the seven explicit-only skills, and prepared STOP-line launches that meet the conditions below. At involve=low, the requested workflow also includes the executor chain's routine local implementation, mechanical review fixes, and Git lifecycle described below. Each started run keeps its skill's scope and artifact ownership, the user's limits, and the host's permission requirements.

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: it takes the marked recommendation on routine judgment calls and logs each (§7.8). At low, the requested workflow includes the executor's recommended in-scope 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. Reuse that workflow decision and log each operation; obtain any approval the host separately requires. Review fixes that require deletion are skipped and routed. Retain the merged execution branch. Pass the internal auto=unattended token to the executor and code reviewer with the originating user request, goal and limits in the dispatch brief or run record (conventions §10.7); the token only carries that existing scope and 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, no additional workflow cost ceiling was set: prepared commands may launch within the goal after their resource scope and cost are assessed, their review is current, and host permission allows them (§2). Either way every launch is logged in the decisions record with its stated cost. Apart from the clean worktree removal above, neither the request 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 — retain the state and report the missing specific authority.
• What remains is the goal. No goal — ask for one; never infer a goal from the repository.