@benzotti/jedi 0.1.8 → 0.1.9

package/action/workflow-template.yml

@@ -61,6 +61,7 @@ jobs:
             .jdi/persistence/
             .jdi/framework/
             .jdi/config/
+            .claude/
           key: jedi-state-${{ github.repository }}-${{ github.head_ref || github.ref_name }}
           restore-keys: |
             jedi-state-${{ github.repository }}-main
@@ -79,63 +80,14 @@ jobs:
           fi
           mkdir -p .jdi/persistence
 
-      # Run Jedi via the official Claude Code Action
+      # Run Jedi via the official Claude Code Action (tag mode — posts comments automatically)
+      # NOTE: No 'prompt' input — Jedi instructions live in .claude/CLAUDE.md (written by bootstrap)
+      # Using prompt would switch to agent mode which doesn't post comments back to the PR/issue
       - name: Run Jedi
         uses: anthropics/claude-code-action@v1
         with:
           anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
           trigger_phrase: '@jedi'
-          prompt: |
-            You are Jedi, an AI development framework that uses specialised agents to plan, implement, review, and ship features.
-
-            IMPORTANT: You are running inside a GitHub Action. Your final text response will be posted as a comment on the issue/PR. You MUST always end with a clear, well-formatted markdown summary of what you did, what was created, and what the user should do next. Never end on a tool call without a text response — the user will see nothing if you do.
-
-            ## Framework
-
-            Read `.jdi/framework/components/meta/AgentBase.md` for the base agent protocol.
-            Your framework files are in `.jdi/framework/` — agents, components, learnings, and teams.
-            Your state is tracked in `.jdi/config/state.yaml`.
-            Plans live in `.jdi/plans/`.
-
-            ## Learnings
-
-            IMPORTANT: Always read learnings BEFORE starting any work.
-            Check `.jdi/persistence/learnings.md` for accumulated team learnings and preferences.
-            Check `.jdi/framework/learnings/` for categorised learnings (backend, frontend, testing, devops, general).
-            These learnings represent the team's coding standards — follow them.
-            When you learn something new from a review or feedback, update the appropriate learnings file
-            AND write the consolidated version to `.jdi/persistence/learnings.md`.
-
-            ## Codebase Index
-
-            Check `.jdi/persistence/codebase-index.md` for an indexed representation of the codebase.
-            If it exists, use it for faster navigation. If it doesn't, consider generating one
-            and saving it to `.jdi/persistence/codebase-index.md` for future runs.
-
-            ## Workflow Routing
-
-            Based on the user's request, follow the appropriate workflow:
-
-            - **Plan requests** ("plan", "design", or ClickUp ticket URLs): Read `.jdi/framework/agents/jdi-planner.md` and create a plan in `.jdi/plans/`. Present a summary and ask for feedback.
-            - **Implementation** ("implement", "build", "execute"): Read the current plan from state.yaml, use `.jdi/framework/components/meta/ComplexityRouter.md` to decide single-agent vs teams mode.
-            - **Quick changes** ("quick", "fix", "small"): Make minimal focused changes. Commit when done.
-            - **Review** ("review"): Review PR changes using `.jdi/framework/components/quality/PRReview.md`.
-            - **PR feedback** ("feedback"): Address review comments using `.jdi/framework/agents/jdi-pr-feedback.md`. Extract learnings from reviewer preferences.
-            - **"do" + ClickUp URL**: Full flow — plan from ticket, then implement.
-
-            ## Iterative Refinement
-
-            After completing any workflow, present a summary and ask for feedback.
-            When the user provides feedback, apply changes incrementally — do not restart from scratch.
-            When the user approves ("approved", "lgtm", "looks good"), finalise the work.
-
-            ## ClickUp Integration
-
-            If the user provides a ClickUp URL, fetch the ticket details:
-            ```bash
-            curl -s -H "Authorization: $CLICKUP_API_TOKEN" "https://api.clickup.com/api/v2/task/{task_id}"
-            ```
-            Use the ticket name, description, and checklists as requirements.
         env:
           CLICKUP_API_TOKEN: ${{ secrets.CLICKUP_API_TOKEN }}
 
@@ -148,6 +100,7 @@ jobs:
             .jdi/persistence/
             .jdi/framework/
             .jdi/config/
+            .claude/
           key: jedi-state-${{ github.repository }}-${{ github.head_ref || github.ref_name }}-${{ github.run_id }}
 
   # ── Promote learnings to main baseline when PRs merge ──
@@ -165,6 +118,7 @@ jobs:
             .jdi/persistence/
             .jdi/framework/
             .jdi/config/
+            .claude/
           key: jedi-state-${{ github.repository }}-main-promotion-${{ github.sha }}
           restore-keys: |
             jedi-state-${{ github.repository }}-
@@ -177,4 +131,5 @@ jobs:
             .jdi/persistence/
             .jdi/framework/
             .jdi/config/
+            .claude/
           key: jedi-state-${{ github.repository }}-main-${{ github.sha }}

package/dist/index.js

@@ -9244,7 +9244,7 @@ async function detectProjectType(cwd) {
 // src/utils/copy-framework.ts
 import { join as join2, dirname } from "path";
 import { existsSync as existsSync2, mkdirSync } from "fs";
-async function copyFrameworkFiles(cwd, projectType, force) {
+async function copyFrameworkFiles(cwd, projectType, force, ci = false) {
   const frameworkDir = join2(import.meta.dir, "../framework");
   const frameworkDest = join2(cwd, ".jdi", "framework");
   const glob = new Bun.Glob("**/*");
@@ -9287,9 +9287,65 @@ async function copyFrameworkFiles(cwd, projectType, force) {
     await Bun.write(dest, content);
   }
   const claudeMdPath = join2(cwd, ".claude", "CLAUDE.md");
-  const routingHeader = "## JDI Workflow Routing";
-  if (!existsSync2(claudeMdPath)) {
-    await Bun.write(claudeMdPath, `${routingHeader}
+  const claudeDir = join2(cwd, ".claude");
+  if (!existsSync2(claudeDir))
+    mkdirSync(claudeDir, { recursive: true });
+  if (ci) {
+    await Bun.write(claudeMdPath, `# Jedi AI Development Framework
+
+You are Jedi, an AI development framework that uses specialised agents to plan, implement, review, and ship features.
+
+## Framework
+
+Read \`.jdi/framework/components/meta/AgentBase.md\` for the base agent protocol.
+Your framework files are in \`.jdi/framework/\` \u2014 agents, components, learnings, and teams.
+Your state is tracked in \`.jdi/config/state.yaml\`.
+Plans live in \`.jdi/plans/\`.
+
+## Learnings
+
+IMPORTANT: Always read learnings BEFORE starting any work.
+Check \`.jdi/persistence/learnings.md\` for accumulated team learnings and preferences.
+Check \`.jdi/framework/learnings/\` for categorised learnings (backend, frontend, testing, devops, general).
+These learnings represent the team's coding standards \u2014 follow them.
+When you learn something new from a review or feedback, update the appropriate learnings file
+AND write the consolidated version to \`.jdi/persistence/learnings.md\`.
+
+## Codebase Index
+
+Check \`.jdi/persistence/codebase-index.md\` for an indexed representation of the codebase.
+If it exists, use it for faster navigation. If it doesn't, consider generating one
+and saving it to \`.jdi/persistence/codebase-index.md\` for future runs.
+
+## Workflow Routing
+
+Based on the user's request, follow the appropriate workflow:
+
+- **Plan requests** ("plan", "design", or ClickUp ticket URLs): Read \`.jdi/framework/agents/jdi-planner.md\` and create a plan in \`.jdi/plans/\`. Present a summary and ask for feedback.
+- **Implementation** ("implement", "build", "execute"): Read the current plan from state.yaml, use \`.jdi/framework/components/meta/ComplexityRouter.md\` to decide single-agent vs teams mode.
+- **Quick changes** ("quick", "fix", "small"): Make minimal focused changes. Commit when done.
+- **Review** ("review"): Review PR changes using \`.jdi/framework/components/quality/PRReview.md\`.
+- **PR feedback** ("feedback"): Address review comments using \`.jdi/framework/agents/jdi-pr-feedback.md\`. Extract learnings from reviewer preferences.
+- **"do" + ClickUp URL**: Full flow \u2014 plan from ticket, then implement.
+
+## Iterative Refinement
+
+After completing any workflow, present a summary and ask for feedback.
+When the user provides feedback, apply changes incrementally \u2014 do not restart from scratch.
+When the user approves ("approved", "lgtm", "looks good"), finalise the work.
+
+## ClickUp Integration
+
+If the user provides a ClickUp URL, fetch the ticket details:
+\`\`\`bash
+curl -s -H "Authorization: $CLICKUP_API_TOKEN" "https://api.clickup.com/api/v2/task/{task_id}"
+\`\`\`
+Use the ticket name, description, and checklists as requirements.
+`);
+  } else {
+    const routingHeader = "## JDI Workflow Routing";
+    if (!existsSync2(claudeMdPath)) {
+      await Bun.write(claudeMdPath, `${routingHeader}
 
 Recognise natural language JDI intents and invoke the matching skill via the Skill tool. Pass the user's full message as the argument.
 
@@ -9307,10 +9363,10 @@ Extract flags from context: "in a worktree" \u2192 \`--worktree\`, "lightweight"
 
 After \`/jdi:create-plan\` or \`/jdi:implement-plan\` completes, the conversation continues naturally \u2014 no new command invocation needed. When the user provides feedback (e.g. "change task 2", "move this to a helper", "add error handling"), apply the changes directly, update state, and present the updated summary. When the user approves (e.g. "approved", "looks good", "lgtm"), finalise the review state. The conversation IS the feedback loop.
 `);
-  } else {
-    const existing = await Bun.file(claudeMdPath).text();
-    if (!existing.includes(routingHeader)) {
-      await Bun.write(claudeMdPath, existing + `
+    } else {
+      const existing = await Bun.file(claudeMdPath).text();
+      if (!existing.includes(routingHeader)) {
+        await Bun.write(claudeMdPath, existing + `
 ` + `${routingHeader}
 
 Recognise natural language JDI intents and invoke the matching skill via the Skill tool. Pass the user's full message as the argument.
@@ -9329,6 +9385,7 @@ Extract flags from context: "in a worktree" \u2192 \`--worktree\`, "lightweight"
 
 After \`/jdi:create-plan\` or \`/jdi:implement-plan\` completes, the conversation continues naturally \u2014 no new command invocation needed. When the user provides feedback (e.g. "change task 2", "move this to a helper", "add error handling"), apply the changes directly, update state, and present the updated summary. When the user approves (e.g. "approved", "looks good", "lgtm"), finalise the review state. The conversation IS the feedback loop.
 `);
+      }
     }
   }
 }
@@ -9378,7 +9435,7 @@ var initCommand = defineCommand({
     for (const dir of dirs) {
       await Bun.write(join3(cwd, dir, ".gitkeep"), "");
     }
-    await copyFrameworkFiles(cwd, projectType, args.force);
+    await copyFrameworkFiles(cwd, projectType, args.force, args.ci);
     if (args.storage || args["storage-path"]) {
       const { parse, stringify } = await Promise.resolve().then(() => __toESM(require_dist(), 1));
       const configPath = join3(cwd, ".jdi", "config", "jdi-config.yaml");
@@ -11431,7 +11488,7 @@ var setupActionCommand = defineCommand({
 // package.json
 var package_default = {
   name: "@benzotti/jedi",
-  version: "0.1.8",
+  version: "0.1.9",
   description: "JDI - Context-efficient AI development framework for Claude Code",
   type: "module",
   bin: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@benzotti/jedi",
-  "version": "0.1.8",
+  "version": "0.1.9",
   "description": "JDI - Context-efficient AI development framework for Claude Code",
   "type": "module",
   "bin": {