@chamba/claude-extras 0.3.0 → 0.3.2

package/assets/commands/ticket.md

@@ -3,25 +3,31 @@ description: Resolve a ticket end-to-end in isolated worktrees, delegating to ch
 argument-hint: <ticket> [repo ...]
 ---
 
-You are orchestrating ticket **$ARGUMENTS** end-to-end. chamba provides the
-worktrees, context, plan validation and vault memory; you delegate the thinking
-and the code to the configured subagents. **Run to the end and stop only for my
-final review** — do not pause for approval mid-way.
+You are orchestrating ticket **$ARGUMENTS** end-to-end. chamba provides context,
+plan validation, worktrees and vault memory; you delegate the thinking and the
+code to the configured subagents. **Run to the end and stop only for my final
+review** — do not pause for approval mid-way.
 
-1. Create isolated worktrees: call `chamba_create_worktrees` with the ticket id
-   (and the repos if I named any). ALL work happens INSIDE these worktrees —
-   never edit the main checkouts. Note the branch and per-repo worktree paths.
-2. Call `chamba_load_context` with the ticket to pull the workspace map + relevant
-   Obsidian notes.
-3. Delegate to the **planner** subagent to produce the detailed plan. Run it
-   through `chamba_review_plan`; if not approved, fix and re-review (max 3 rounds).
-   Also have the **reviewer** subagent audit it. Do all of this WITHOUT stopping to
-   ask me — the heuristic review + the reviewer agent are the quality gate.
-4. For each subtask/repo, delegate implementation to the **implementer** subagent,
-   working only in that repo's worktree. Delegate the tests to the **tester**
-   subagent and run them.
-5. Call `chamba_summarize_to_vault` with a summary of what changed.
-6. STOP and report for my review: per repo, what changed and the test results; the
-   `.code-workspace` to open; and the suggested commit + `git merge --no-ff`
-   commands. Do NOT commit, merge or push — I review, commit and send to my
-   company's code review by hand.
+The first token of the arguments is the ticket id; any further tokens are repos I
+named explicitly. Analyze first, create worktrees only for the repos actually
+touched — do not create a worktree for every repo in the workspace.
+
+1. Call `chamba_load_context` with the ticket to pull the workspace map (all repos
+   and what each one is) + relevant Obsidian notes.
+2. Delegate to the **planner** subagent to produce the plan. The plan MUST state
+   **which repos the ticket touches and why**, with subtasks grouped per repo. If I
+   named repos in the arguments, use exactly those; otherwise infer the set from the
+   ticket + the workspace map. If anything is ambiguous, list it as an assumption —
+   do not invent scope.
+3. Run the plan through `chamba_review_plan` and have the **reviewer** subagent
+   audit it. Fix and re-review until approved (max 3 rounds). Do NOT stop to ask me.
+4. Create isolated worktrees ONLY for the repos the plan identified: call
+   `chamba_create_worktrees` with the ticket and that repo list. ALL work happens
+   inside these worktrees — never edit the main checkouts.
+5. For each subtask/repo, delegate implementation to the **implementer** subagent
+   (in that repo's worktree) and the tests to the **tester** subagent; run them.
+6. Call `chamba_summarize_to_vault` with a summary of what changed.
+7. STOP and report for my review: the repos touched and why; per repo, what changed
+   and the test results; the `.code-workspace` to open; and the suggested commit +
+   `git merge --no-ff` commands. Do NOT commit, merge or push — I review, commit and
+   send to my company's code review by hand.

package/assets/commands/vault.md

@@ -0,0 +1,13 @@
+---
+description: Show the connected Obsidian vault and the notes chamba can see
+---
+
+Call `chamba_vault_status` and show me the result clearly:
+
+- The resolved vault path and whether it came from `CHAMBA_OBSIDIAN_VAULT_PATH`
+  or autodetection.
+- How many markdown notes chamba can see, and the list of note files.
+
+If no vault is found, or the note count is 0, or the path ends in `.obsidian`,
+tell me to set `CHAMBA_OBSIDIAN_VAULT_PATH` to the **vault root** (the folder that
+*contains* `.obsidian`, not `.obsidian` itself) and restart the editor.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chamba/claude-extras",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "description": "Optional Claude Code extras for chamba: slash commands, subagents and hooks installer",
   "license": "MIT",
   "type": "module",
@@ -31,8 +31,8 @@
   ],
   "dependencies": {
     "@inquirer/prompts": "^7.0.0",
-    "@chamba/adapters": "0.3.0",
-    "@chamba/core": "0.3.0"
+    "@chamba/adapters": "0.3.2",
+    "@chamba/core": "0.3.2"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",