@infinitedusky/indusk-mcp 1.24.1 → 1.24.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/work.md +10 -5
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@infinitedusky/indusk-mcp",
3
- "version": "1.24.1",
3
+ "version": "1.24.2",
4
4
  "description": "InDusk development system — skills, MCP tools, and CLI for structured AI-assisted development",
5
5
  "type": "module",
6
6
  "files": [
package/skills/work.md CHANGED
@@ -276,12 +276,17 @@ Skip silently if `mcp__indusk__highlight` is unavailable — highlights are best
276
276
 
277
277
  ## Commits (jj)
278
278
 
279
- Use the **describe-then-do** workflow from the jj skill:
279
+ Use the **describe-then-do** workflow from the jj skill. The order is load-bearing — never reverse it.
280
280
 
281
- 1. `jj new` before each logical unit of work
282
- 2. `jj describe` to declare what you're about to do
283
- 3. Do the work, check off the item
284
- 4. Repeat
281
+ **For every checklist item, in this exact order:**
282
+
283
+ 1. **`jj new`** — start a fresh empty commit. Do this BEFORE you touch any file.
284
+ 2. **`jj describe -m "..."`** — write the commit message describing what you're ABOUT to do. The description names the intent in present/future tense ("rename foo to bar") not past tense ("renamed foo to bar").
285
+ 3. **Do the work** — edit files, run tools, accumulate changes in `@` (the current commit).
286
+ 4. **Check the item off** in the impl.md.
287
+ 5. **Repeat** for the next item — back to step 1.
288
+
289
+ **❌ Anti-pattern: describe-after-do.** Doing the work first and then describing what you did breaks two things: (a) the eval agent fires on `jj describe`, so the description is what it scores against — late descriptions mean the agent scores work that's already done without intent context; (b) the working copy IS the current commit in jj, so any uncommitted state automatically gets attributed to whatever the commit description currently says, even if that's the previous unit's description. Always: new → describe → work, in that order.
285
290
 
286
291
  **Default: one commit per checklist item.** Each impl checklist item is a logical unit of work — give it its own commit. This keeps history granular, makes blame and bisect useful, avoids the end-of-phase `jj split` chore, and lets the eval agent score each unit while context is fresh.
287
292