@benzotti/jedi 0.1.0

package/framework/hooks/lint-fix-frontend.md

@@ -0,0 +1,59 @@
+---
+name: lint-fix-frontend
+description: Auto-fix ESLint issues on frontend files after edit
+trigger: PostToolUse (Edit|Write)
+type: claude-code-hook
+---
+
+# Lint Fix Frontend Hook
+
+Automatically runs `bun run lint:fix` after Claude Code (or an agent) edits or writes a file.
+
+---
+
+## Trigger
+
+Fires when:
+- Claude Code edits a file (Edit tool)
+- Claude Code writes a file (Write tool)
+- Any JDI agent edits/writes files via subagents
+
+**Claude Code event:** `PostToolUse` with matcher `Edit|Write`
+
+---
+
+## Behaviour
+
+Runs `bun run lint:fix` (`turbo lint -- --fix`) asynchronously in the background so Claude is not blocked. Covers all frontend workspaces via turbo.
+
+---
+
+## Installation
+
+Registered automatically by `/jdi:init` in `.claude/settings.local.json`:
+
+```json
+{
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Edit|Write",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bun run lint:fix",
+            "timeout": 30,
+            "async": true
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+---
+
+## Manual Override
+
+To temporarily disable, remove the `PostToolUse` entry from `.claude/settings.local.json`.

package/framework/hooks/on-pause.md

@@ -0,0 +1,213 @@
+---
+name: on-pause
+description: Actions to perform when work is paused, generates continuation file
+trigger: pause_request
+---
+
+# On-Pause Hook
+
+Actions performed when the user requests to pause work or when a session ends naturally.
+
+---
+
+## Trigger
+
+Fires when:
+- User explicitly requests to pause (`/jdi:pause`)
+- Session is ending (user leaves)
+- Blocking issue encountered (Rule 4 deviation)
+- Checkpoint requires extended user action
+
+---
+
+## Purpose
+
+Create a continuation file that enables seamless resumption:
+1. Capture current position precisely
+2. Record context that would be lost
+3. Provide clear next action
+4. Enable fresh context resumption
+
+---
+
+## Actions
+
+### 1. Capture Current State
+
+```bash
+# Read current state
+cat .jdi/config/state.yaml
+
+# Extract position
+PHASE=$(yq -r '.position.phase' .jdi/config/state.yaml)
+PLAN=$(yq -r '.position.plan' .jdi/config/state.yaml)
+TASK=$(yq -r '.position.task' .jdi/config/state.yaml)
+STATUS=$(yq -r '.position.status' .jdi/config/state.yaml)
+```
+
+### 2. Identify Next Action
+
+Based on current status, determine what should happen next:
+
+| Status | Next Action |
+|--------|-------------|
+| `planning` | Continue planning |
+| `executing` | Resume task execution |
+| `verifying` | Complete verification |
+| `blocked` | Resolve blocker |
+| `checkpoint` | Await user response |
+
+### 3. Capture Session Context
+
+Gather context that would be lost:
+- Recent decisions made
+- Key discoveries
+- Warnings or concerns
+- User preferences expressed
+
+### 4. Generate Continuation File
+
+Create `.jdi/CONTINUE-HERE.md`:
+
+```markdown
+---
+paused_at: {ISO timestamp}
+phase: {N}
+plan: {NN}
+task: {N or null}
+status: {status}
+---
+
+# Continue Here
+
+## Quick Resume
+
+**Last completed:** {description of last completed work}
+**Current status:** {what's in progress}
+**Next action:** `{command to run}`
+
+## Position
+
+| Level | Value | Name |
+|-------|-------|------|
+| Phase | {N} | {phase_name} |
+| Plan | {NN} | {plan_name} |
+| Task | {N} | {task_name or "N/A"} |
+| Status | {status} | |
+
+## Context from This Session
+
+### Decisions Made
+{List of decisions made during this session}
+
+### Key Discoveries
+{Important findings or learnings}
+
+### Warnings/Concerns
+{Any issues to be aware of}
+
+### User Preferences
+{Any preferences expressed by user}
+
+## To Resume
+
+### Option 1: Continue Where Left Off
+```bash
+/jdi:resume
+```
+
+### Option 2: Manual Resume
+```bash
+# If task was in progress:
+/jdi:implement-plan {phase}-{plan} --resume-from-task {task}
+
+# If planning:
+/jdi:create-plan {phase}
+
+# If verifying:
+/jdi:verify {phase}
+```
+
+## Recent Commits
+
+| Time | Hash | Message |
+|------|------|---------|
+{List recent commits from session}
+
+## Files Modified (Uncommitted)
+
+```bash
+git status --short
+```
+
+{Output of uncommitted changes, if any}
+
+## Blockers (if any)
+
+{Description of any blocking issues}
+
+---
+
+*Generated by JDI on-pause hook at {timestamp}*
+```
+
+### 5. Update State
+
+Mark session as paused:
+
+```yaml
+position:
+  status: paused
+session:
+  paused_at: "{timestamp}"
+  continuation_file: ".jdi/CONTINUE-HERE.md"
+```
+
+### 6. Display Pause Summary
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ JDI ► SESSION PAUSED
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Paused at: Phase {N}, Plan {NN}, Task {N}
+Status: {status}
+
+Continuation file: .jdi/CONTINUE-HERE.md
+
+To resume: /jdi:resume
+
+───────────────────────────────────────────────────────
+```
+
+---
+
+## Continuation File Location
+
+The continuation file is always at: `.jdi/CONTINUE-HERE.md`
+
+This file is:
+- Overwritten on each pause (only one active)
+- Deleted after successful resume
+- Human-readable for manual recovery
+
+---
+
+## Integration with Resume
+
+The `/jdi:resume` command:
+1. Reads `.jdi/CONTINUE-HERE.md`
+2. Loads context specified in the file
+3. Executes the `next_action`
+4. Deletes the continuation file on success
+
+---
+
+## Success Criteria
+
+- [ ] Current position captured accurately
+- [ ] Next action clearly identified
+- [ ] Session context preserved
+- [ ] Continuation file is self-contained
+- [ ] State updated to paused
+- [ ] User informed of how to resume

package/framework/hooks/pre-commit.md

@@ -0,0 +1,143 @@
+---
+name: pre-commit
+description: Validation before creating a commit
+trigger: commit_attempt
+---
+
+# Pre-Commit Hook
+
+Validation performed before creating any commit.
+
+---
+
+## Trigger
+
+Fires when:
+- <JDI:Commit /> component invoked
+- `/jdi-commit` command run
+- Manual commit through JDI workflow
+
+---
+
+## Validation Steps
+
+### 1. Check Staged Files
+
+```bash
+git diff --cached --name-only
+```
+
+**Verify:**
+- At least one file staged
+- No unintended files (logs, secrets, temp)
+- Files match expected task files
+
+### 1b. CRITICAL: Validate Excluded Directories
+
+**The following directories must NEVER be staged:**
+- `.worktrees/**` - Git worktrees are execution infrastructure
+- `.jdi/**` - JDI runtime state and configuration
+
+```bash
+# Check for excluded files in staging
+EXCLUDED=$(git diff --cached --name-only | grep -E "^(\.worktrees/|\.jdi/)")
+if [ -n "$EXCLUDED" ]; then
+  echo "ERROR: Excluded directories found in staging:"
+  echo "$EXCLUDED"
+  echo ""
+  echo "These directories must not be committed:"
+  echo "  .worktrees/ - Git worktrees are execution infrastructure"
+  echo "  .jdi/       - JDI runtime state and configuration"
+  echo ""
+  echo "Unstage these files with: git reset HEAD <file>"
+  exit 1
+fi
+```
+
+**If excluded files found:**
+- **BLOCK COMMIT** (no override allowed)
+- Display error message
+- List offending files
+- Provide unstaging instructions
+
+### 2. Run Quality Checks
+
+```bash
+# TypeScript check (if applicable)
+bun run typecheck 2>&1 | head -20
+
+# Lint check (if applicable)
+bun run lint 2>&1 | head -20
+```
+
+**If errors:**
+- Block commit
+- Display errors
+- Suggest fixes
+
+### 3. Check for Secrets
+
+```bash
+# Common secret patterns
+grep -r -E "(API_KEY|SECRET|PASSWORD|TOKEN)=" --include="*.ts" --include="*.tsx" --include="*.env" .
+```
+
+**If found:**
+- Block commit
+- Warn about potential secrets
+- Require confirmation to proceed
+
+### 4. Validate Commit Message
+
+Check message format:
+```
+{type}({scope}): {description}
+```
+
+**Valid types:** feat, fix, refactor, docs, test, chore, perf, style
+
+**Validation:**
+- First line ≤72 characters
+- Imperative mood
+- No period at end
+- Scope matches task context
+
+### 5. Check for Large Files
+
+```bash
+git diff --cached --stat | grep -E "\+[0-9]{4,}"
+```
+
+**If large additions:**
+- Warn about file size
+- Confirm intentional
+
+---
+
+## Blocking Conditions
+
+Commit is blocked if:
+- **Files in `.worktrees/` or `.jdi/` are staged** (NO OVERRIDE ALLOWED)
+- Type check fails
+- Lint errors exist (not warnings)
+- Secrets detected (without override)
+- Message format invalid
+- No files staged
+
+---
+
+## Override
+
+Allow override with:
+- `--no-verify` flag (use sparingly)
+- Explicit confirmation for warnings
+
+---
+
+## Outputs
+
+| Output | Purpose |
+|--------|---------|
+| Pass/Fail | Gate decision |
+| Errors | What needs fixing |
+| Warnings | What to review |