habit

/habit: Entry Point & Browse

This skill is the main entry point for the Habit system. Route based on what the user is asking for:

Triggers

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

Routing

• Browsing/searching/listing → handle below.
• Viewing full details ("show me X", "what does X do") → guide to /habit:edit <id> (shows full content when no changes are provided).
• Creating or editing → guide to /habit:edit <id> <description>.
• Running a specific habit → guide to /habit:run <id> [override].
• Applying relevant habits to a request → guide to /habit:suggest <request>.
• Watching/observing → guide to /habit:watch.
• Extracting/sweeping → guide to /habit:distill.
• User asks what habits are or how the system works → explain briefly and point to /habit:edit or /habit:watch.

After routing the user to another command, stop. Do not also execute the Browse & Select flow below.

Output: the routing message or the browse list.

Index (merged, project shadows global)

!bash ${CLAUDE_PLUGIN_ROOT}/bin/habit-tools.sh read-index merged

Browse & Select

1. $ARGUMENTS empty → list all. Non-empty → search query.

2. The merged index is already loaded. Each entry has a scope field (global or project). Show [G]/[P] indicators. Exclude archived.

3. If searching, fuzzy-match query against id, tags, description. Show only entries that match. If nothing matches, say so and suggest creating one or trying a different search.

4. Numbered list of matching entries, one line each: N. [scope] id tags description. Never mention archived entries to the user.

5. After list:

   Pick a number or name to run, add context for an override (e.g. "1 only in auth" or "fix-types in auth"), or say "edit N" to modify.

6. When user picks one: guide to /habit:run <id> [override].

7. Empty inventory:

   No habits yet. Create one with /habit:edit <name> <description> or start watching with /habit:watch.