@benzotti/jedi 0.1.2 → 0.1.4

package/action/action.yml

@@ -0,0 +1,108 @@
+name: 'Jedi AI Developer'
+description: 'AI-powered development workflows using the Jedi framework, powered by anthropic/claude-code-action'
+author: 'benzotti'
+
+inputs:
+  anthropic_api_key:
+    description: 'Anthropic API key for Claude'
+    required: true
+  clickup_api_token:
+    description: 'ClickUp API token for ticket fetching (optional)'
+    required: false
+    default: ''
+  allowed_users:
+    description: 'Comma-separated GitHub usernames allowed to trigger (empty = repo collaborators with write access)'
+    required: false
+    default: ''
+  trigger_phrase:
+    description: 'The trigger phrase to look for in comments'
+    required: false
+    default: '@jedi'
+  jedi_version:
+    description: 'Version of @benzotti/jedi to install for init'
+    required: false
+    default: 'latest'
+  claude_code_action_version:
+    description: 'Version of anthropic/claude-code-action to use'
+    required: false
+    default: 'v1'
+
+outputs:
+  session_id:
+    description: 'Claude Code session ID for conversation continuity'
+    value: ${{ steps.claude.outputs.session_id }}
+  execution_file:
+    description: 'Path to Claude Code execution output'
+    value: ${{ steps.claude.outputs.execution_file }}
+
+runs:
+  using: 'composite'
+  steps:
+    # Ensure Jedi framework is initialised in the repo
+    - name: Bootstrap Jedi framework
+      shell: bash
+      run: |
+        if [ ! -d ".jdi/framework" ]; then
+          echo "Jedi framework not found — initialising..."
+          npx @benzotti/jedi@${{ inputs.jedi_version }} init --ci
+        fi
+
+        # Ensure persistence directory exists
+        mkdir -p .jdi/persistence
+
+    # Run Claude Code Action with Jedi-specific configuration
+    - name: Run Claude with Jedi framework
+      id: claude
+      uses: anthropics/claude-code-action@${{ inputs.claude_code_action_version }}
+      with:
+        anthropic_api_key: ${{ inputs.anthropic_api_key }}
+        trigger_phrase: ${{ inputs.trigger_phrase }}
+        prompt: |
+          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/` — agents, components, learnings, and teams.
+          Your state is tracked in `.jdi/config/state.yaml`.
+          Plans live in `.jdi/plans/`.
+
+          ## Learnings
+
+          Check `.jdi/persistence/learnings.md` for accumulated team learnings and preferences.
+          Check `.jdi/framework/learnings/` for categorised learnings (backend, frontend, testing, devops, general).
+          When you learn something from a review or feedback, update the appropriate learnings file.
+
+          ## 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 using the ClickUp API:
+          ```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.
+
+        claude_args: '--permission-mode bypassPermissions'
+
+      env:
+        CLICKUP_API_TOKEN: ${{ inputs.clickup_api_token }}
+
+branding:
+  icon: 'zap'
+  color: 'purple'

package/action/workflow-template.yml

@@ -0,0 +1,172 @@
+# Jedi AI Developer — GitHub Actions Workflow
+# Copy this file to .github/workflows/jedi.yml in your repository
+#
+# Prerequisites:
+#   1. Set ANTHROPIC_API_KEY secret in your repo settings
+#   2. That's it — Jedi bootstraps everything else automatically
+#
+# Optional:
+#   - Set CLICKUP_API_TOKEN secret for ClickUp ticket integration
+#   - Run `npx @benzotti/jedi init` locally to customise framework files
+#
+# Usage: Comment on any issue or PR with @jedi followed by a command:
+#   @jedi plan <description>        — Create an implementation plan
+#   @jedi quick <description>       — Make a small, focused change
+#   @jedi review                    — Review the current PR
+#   @jedi feedback                  — Address PR review comments
+#   @jedi do <clickup-ticket-url>   — Full flow: plan + implement from ticket
+#
+# Conversation: Jedi supports back-and-forth iteration. After Jedi responds,
+# reply with feedback to refine, or say "approved" to finalise.
+#
+# Learnings: Jedi accumulates team preferences across PRs automatically.
+# No files to commit — everything lives in the GitHub Actions cache.
+
+name: Jedi
+
+on:
+  issue_comment:
+    types: [created]
+  pull_request_review_comment:
+    types: [created]
+  push:
+    branches: [main, master]
+
+permissions:
+  contents: write
+  pull-requests: write
+  issues: write
+
+jobs:
+  # ── Triggered by @jedi comments on issues/PRs ──
+  jedi:
+    if: >-
+      (github.event_name == 'issue_comment' || github.event_name == 'pull_request_review_comment')
+      && contains(github.event.comment.body, '@jedi')
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: ${{ github.head_ref || github.ref }}
+
+      # Restore persisted Jedi state (learnings + codebase-index)
+      # 1. Exact match for this branch
+      # 2. Fall back to main baseline (accumulated from all merged PRs)
+      # 3. Fall back to any branch prefix match
+      - name: Restore Jedi state
+        uses: actions/cache@v4
+        with:
+          path: |
+            .jdi/persistence/
+            .jdi/framework/
+            .jdi/config/
+          key: jedi-state-${{ github.repository }}-${{ github.head_ref || github.ref_name }}
+          restore-keys: |
+            jedi-state-${{ github.repository }}-main
+            jedi-state-${{ github.repository }}-
+
+      # Bootstrap Jedi framework if not present (first run or cache miss)
+      - name: Bootstrap Jedi
+        run: |
+          if [ ! -d ".jdi/framework" ]; then
+            npx @benzotti/jedi@latest init --ci
+          fi
+          mkdir -p .jdi/persistence
+
+      # Run Jedi via the official Claude Code Action
+      - 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.
+
+            ## 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 }}
+
+      # Save Jedi state — framework, config, persistence all cached together
+      - name: Save Jedi state
+        if: always()
+        uses: actions/cache/save@v4
+        with:
+          path: |
+            .jdi/persistence/
+            .jdi/framework/
+            .jdi/config/
+          key: jedi-state-${{ github.repository }}-${{ github.head_ref || github.ref_name }}-${{ github.run_id }}
+
+  # ── Promote learnings to main baseline when PRs merge ──
+  promote-learnings:
+    if: github.event_name == 'push'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Restore latest Jedi state
+        id: restore
+        uses: actions/cache@v4
+        with:
+          path: |
+            .jdi/persistence/
+            .jdi/framework/
+            .jdi/config/
+          key: jedi-state-${{ github.repository }}-main-promotion-${{ github.sha }}
+          restore-keys: |
+            jedi-state-${{ github.repository }}-
+
+      - name: Promote to main baseline
+        if: steps.restore.outputs.cache-hit != ''
+        uses: actions/cache/save@v4
+        with:
+          path: |
+            .jdi/persistence/
+            .jdi/framework/
+            .jdi/config/
+          key: jedi-state-${{ github.repository }}-main-${{ github.sha }}