jettypod 4.4.89 → 4.4.91

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.
package/hooks/pre-commit CHANGED
@@ -38,12 +38,14 @@ function checkBranchRestriction() {
38
38
  console.error('❌ Direct commits to main are not allowed');
39
39
  console.error('━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━');
40
40
  console.error('');
41
- console.error('Use the JettyPod workflow instead:');
41
+ console.error('You edited files without starting a worktree first.');
42
+ console.error('Your changes exist but cannot be committed here.');
42
43
  console.error('');
43
- console.error(' jettypod work start <work-item-id>');
44
+ console.error('TO FIX:');
45
+ console.error(' 1. Undo your edits: git checkout .');
46
+ console.error(' 2. Start the workflow: Invoke request-routing skill');
44
47
  console.error('');
45
- console.error('This creates a feature branch where you can commit freely.');
46
- console.error('When done, use \'jettypod work done\' to merge back to main.');
48
+ console.error('The skill creates a worktree where commits are allowed.');
47
49
  console.error('');
48
50
  return false;
49
51
  } catch (err) {
package/jettypod.js CHANGED
@@ -245,16 +245,32 @@ Status: ${currentWork.status}
245
245
  <jettypod_essentials>
246
246
  JettyPod: Structured workflow system with skills that guide complex workflows.
247
247
 
248
- ## ⚠️ CRITICAL: All Work Requires a Work Item
249
- **Claude CANNOT write code directly to main branch.**
250
- - All work requires: \`work create\` \`work start\` skill workflow \`work merge\`
251
- - If user asks to implement something without a work item, create one first and invoke the matching skill
252
- - Pre-commit hooks block direct commits to main
248
+ ## ⚠️ CRITICAL: All Work Starts with request-routing
249
+
250
+ **WHY:** request-routing creates a safe workspace (worktree) where your changes can actually be committed. Without it, you'll edit files on main, then discover the pre-commit hook blocks you—leaving uncommitted changes that can't be saved.
251
+
252
+ **FIRST RESPONSE RULE:** If user describes ANY code change, your FIRST action must be invoking request-routing. Not after reading files. Not after understanding the problem. FIRST.
253
+
254
+ **Trigger phrases → invoke request-routing immediately:**
255
+ - "we should...", "let's...", "can you..." (implementation requests)
256
+ - "fix", "broken", "not working", "bug" (bug reports)
257
+ - "add", "build", "create", "implement" (feature requests)
258
+ - "refactor", "migrate", "upgrade" (technical work)
259
+ - "I noticed...", "I'm thinking..." (when followed by desired change)
260
+
261
+ **⚠️ ANTI-PATTERN: Do NOT edit files before invoking request-routing.**
262
+ Wrong: See problem → edit files → realize you're on main → ask about workflow
263
+ Wrong: Read files → understand problem → try to fix → get blocked → create work item
264
+ Right: User describes work → invoke request-routing → skill creates worktree → then edit
253
265
 
254
266
  ## ⚠️ CRITICAL: Skills are MANDATORY for workflows
255
267
  Skills auto-activate and MUST complete their full workflow:
256
- - epic-planning: Guides architectural decisions
257
- - feature-planning: Guides UX discovery + BDD scenarios
268
+ - **request-routing**: ENTRY POINT - routes ALL work requests to correct skill
269
+ - epic-planning: Guides architectural decisions (invoked by request-routing)
270
+ - feature-planning: Guides UX discovery + BDD scenarios (invoked by request-routing)
271
+ - chore-planning: Guides technical work planning (invoked by request-routing)
272
+ - bug-planning: Guides bug investigation (invoked by request-routing)
273
+ - simple-improvement: Direct implementation for obvious changes (invoked by request-routing)
258
274
  - speed-mode: Implements happy path, THEN auto-invokes stable-mode
259
275
  - stable-mode: Adds error handling to speed implementation
260
276
  - external-transition: Guides launch preparation
@@ -36,12 +36,14 @@ function checkBranchRestriction() {
36
36
  console.error('❌ Direct commits to main are not allowed');
37
37
  console.error('━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━');
38
38
  console.error('');
39
- console.error('Use the JettyPod workflow instead:');
39
+ console.error('You edited files without starting a worktree first.');
40
+ console.error('Your changes exist but cannot be committed here.');
40
41
  console.error('');
41
- console.error(' jettypod work start <work-item-id>');
42
+ console.error('TO FIX:');
43
+ console.error(' 1. Undo your edits: git checkout .');
44
+ console.error(' 2. Start the workflow: Invoke request-routing skill');
42
45
  console.error('');
43
- console.error('This creates a feature branch where you can commit freely.');
44
- console.error('When done, use \'jettypod work done\' to merge back to main.');
46
+ console.error('The skill creates a worktree where commits are allowed.');
45
47
  console.error('');
46
48
  return false;
47
49
  } catch (err) {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "jettypod",
3
- "version": "4.4.89",
3
+ "version": "4.4.91",
4
4
  "description": "AI-powered development workflow manager with TDD, BDD, and automatic test generation",
5
5
  "main": "jettypod.js",
6
6
  "bin": {