run

/habit:run: Execute

Triggers

!bash ${CLAUDE_PLUGIN_ROOT}/bin/habit-tools.sh check-triggers ${CLAUDE_SESSION_ID}

Existing Habit (if any)

!bash ${CLAUDE_PLUGIN_ROOT}/bin/habit-tools.sh read-habit "$0"

Instructions

1. Parse $ARGUMENTS: first token = id, rest = override (may be empty). The habit content is already loaded above.

2. Parse the loaded content:

   • NOT_FOUND: if the argument matches a habit id case-insensitively, load the intended habit via bash ${CLAUDE_PLUGIN_ROOT}/bin/habit-tools.sh read-habit <id>. Otherwise, suggest alternatives from the index and point to /habit.
   • SCOPE:<scope>: note the scope, extract the instruction body (everything after the YAML frontmatter --- block).

3. With override (semantic integration): weave it into the appropriate parts of the instruction. The merged result must read as one coherent prompt.

   Base: "Fix all TypeScript errors. Run tsc --noEmit. Fix file by file." Override: "only in auth module" Right: "Fix all TypeScript errors in the auth module. Run tsc --noEmit scoped to auth files. Fix file by file." Wrong: "Fix all TypeScript errors. Run tsc --noEmit. Fix file by file. only in auth module."

4. Before executing, if the instruction names specific file paths, use the Read tool to verify they exist. If it names CLI tools not commonly installed, note this to the user. Then execute directly. Just do the work as if the user typed the instruction. Do not announce what you're doing, explain the override merge, mention logging, or describe internal operations.

5. After execution, log it silently (the user should not see this):

   bash ${CLAUDE_PLUGIN_ROOT}/bin/habit-tools.sh log-exec <scope> <id> '<override if any>'
   

No arguments → Usage: /habit:run <id> [overrides]. Point to /habit.