aircana 4.0.0.rc2 → 4.0.0.rc3

data/lib/aircana/cli/commands/generate.rb

@@ -1,11 +1,12 @@
 # frozen_string_literal: true
 
-require_relative "../../generators/plan_command_generator"
-require_relative "../../generators/record_command_generator"
-require_relative "../../generators/execute_command_generator"
-require_relative "../../generators/review_command_generator"
-require_relative "../../generators/apply_feedback_command_generator"
-require_relative "../../generators/ask_expert_command_generator"
+# Commands that reference old agent system - commented out for now
+# require_relative "../../generators/plan_command_generator"
+# require_relative "../../generators/record_command_generator"
+# require_relative "../../generators/execute_command_generator"
+# require_relative "../../generators/review_command_generator"
+# require_relative "../../generators/apply_feedback_command_generator"
+# require_relative "../../generators/ask_expert_command_generator"
 require_relative "../../generators/hooks_generator"
 
 module Aircana
@@ -13,14 +14,18 @@ module Aircana
     module Generate
       class << self
         def generators
-          @generators ||= [
-            Aircana::Generators::PlanCommandGenerator.new,
-            Aircana::Generators::RecordCommandGenerator.new,
-            Aircana::Generators::ExecuteCommandGenerator.new,
-            Aircana::Generators::ReviewCommandGenerator.new,
-            Aircana::Generators::ApplyFeedbackCommandGenerator.new,
-            Aircana::Generators::AskExpertCommandGenerator.new
-          ]
+          # No default commands for now - they referenced the old agent system
+          @generators ||= []
+
+          # TODO: Re-enable these when we have a new command system
+          # @generators ||= [
+          #   Aircana::Generators::PlanCommandGenerator.new,
+          #   Aircana::Generators::RecordCommandGenerator.new,
+          #   Aircana::Generators::ExecuteCommandGenerator.new,
+          #   Aircana::Generators::ReviewCommandGenerator.new,
+          #   Aircana::Generators::ApplyFeedbackCommandGenerator.new,
+          #   Aircana::Generators::AskExpertCommandGenerator.new
+          # ]
         end
 
         def run

data/lib/aircana/cli/commands/init.rb

@@ -132,7 +132,6 @@ module Aircana
           Aircana.create_dir_if_needed(commands_dir)
 
           copy_command_files(commands_dir)
-          install_default_agents
         end
 
         def copy_command_files(destination_dir)
@@ -142,33 +141,6 @@ module Aircana
           end
         end
 
-        def install_default_agents
-          agents_dir = Aircana.configuration.agents_dir
-          Aircana.create_dir_if_needed(agents_dir)
-
-          copy_agent_files(agents_dir)
-        end
-
-        def copy_agent_files(destination_dir)
-          agent_files_pattern = File.join(Aircana.configuration.output_dir, "agents", "*.md")
-          Dir.glob(agent_files_pattern).each do |file|
-            agent_name = File.basename(file, ".md")
-            next unless default_agent?(agent_name)
-
-            destination_file = File.join(destination_dir, File.basename(file))
-            # Skip copying if source and destination are the same
-            next if File.expand_path(file) == File.expand_path(destination_file)
-
-            Aircana.human_logger.success("Installing default agent: #{agent_name}")
-            FileUtils.cp(file, destination_dir)
-          end
-        end
-
-        def default_agent?(agent_name)
-          require_relative "../../generators/agents_generator"
-          Aircana::Generators::AgentsGenerator.available_default_agents.include?(agent_name)
-        end
-
         def install_hooks
           scripts_dir = Aircana.configuration.scripts_dir
           return unless Dir.exist?(scripts_dir)
@@ -201,7 +173,7 @@ module Aircana
             "post_tool_use" => { event: "PostToolUse", matcher: nil },
             "user_prompt_submit" => { event: "UserPromptSubmit", matcher: nil },
             "session_start" => { event: "SessionStart", matcher: nil },
-            "refresh_agents" => { event: "SessionStart", matcher: nil },
+            "refresh_skills" => { event: "SessionStart", matcher: nil },
             "notification_sqs" => { event: "Notification", matcher: nil },
             "rubocop_pre_commit" => { event: "PreToolUse", matcher: "Bash" },
             "rspec_test" => { event: "PostToolUse", matcher: "Bash" },
@@ -265,11 +237,11 @@ module Aircana
           Aircana.human_logger.info("\nPlugin structure:")
           Aircana.human_logger.info("  .claude-plugin/plugin.json  - Plugin metadata")
           Aircana.human_logger.info("  commands/                   - Slash commands")
-          Aircana.human_logger.info("  agents/                     - Specialized agents")
+          Aircana.human_logger.info("  agents/                     - Knowledge bases")
           Aircana.human_logger.info("  hooks/                      - Event hook configurations")
           Aircana.human_logger.info("  scripts/                    - Hook scripts and utilities")
           Aircana.human_logger.info("\nNext steps:")
-          Aircana.human_logger.info("  - Create agents: aircana agents create")
+          Aircana.human_logger.info("  - Create knowledge bases: aircana kb create")
           Aircana.human_logger.info("  - Install plugin in Claude Code")
           Aircana.human_logger.info("  - Run: aircana plugin info")
         end

data/lib/aircana/cli/help_formatter.rb

@@ -24,8 +24,7 @@ module Aircana
       def command_groups
         {
           "Knowledge Base Management" => %w[kb],
-          "Hook Management" => %w[hooks],
-          "System" => %w[generate init doctor dump-context]
+          "System" => %w[init doctor]
         }
       end
 

data/lib/aircana/generators/hooks_generator.rb

@@ -11,7 +11,7 @@ module Aircana
         post_tool_use
         user_prompt_submit
         session_start
-        refresh_agents
+        refresh_skills
         notification_sqs
         rubocop_pre_commit
         rspec_test
@@ -21,7 +21,7 @@ module Aircana
       # Default hooks that are auto-installed
       DEFAULT_HOOK_TYPES = %w[
         session_start
-        refresh_agents
+        refresh_skills
         notification_sqs
       ].freeze
 

data/lib/aircana/templates/hooks/refresh_skills.erb

@@ -0,0 +1,121 @@
+#!/bin/bash
+# Auto-refresh remote knowledge bases on session start
+# Runs at most once per 24 hours to avoid API rate limits
+# Only refreshes remote KBs, skips local KBs
+
+set -e
+
+# Create log directory if it doesn't exist
+mkdir -p ~/.aircana
+LOG_FILE="$HOME/.aircana/hooks.log"
+
+# Claude Code provides this environment variable
+PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT}"
+
+if [ -z "$PLUGIN_ROOT" ]; then
+    echo "$(date): Warning - CLAUDE_PLUGIN_ROOT not set, skipping KB refresh" >> "$LOG_FILE"
+    echo "{}"
+    exit 0
+fi
+
+TIMESTAMP_FILE="${PLUGIN_ROOT}/.last_refresh"
+REFRESH_INTERVAL_SECONDS=86400  # 24 hours
+
+# Check if we've refreshed recently
+if [ -f "$TIMESTAMP_FILE" ]; then
+    LAST_REFRESH=$(cat "$TIMESTAMP_FILE")
+    CURRENT_TIME=$(date +%s)
+    TIME_DIFF=$((CURRENT_TIME - LAST_REFRESH))
+
+    if [ $TIME_DIFF -lt $REFRESH_INTERVAL_SECONDS ]; then
+        HOURS_SINCE=$((TIME_DIFF / 3600))
+        echo "$(date): Knowledge bases refreshed ${HOURS_SINCE}h ago, skipping refresh" >> "$LOG_FILE"
+        echo "{}"
+        exit 0
+    fi
+fi
+
+# Tell aircana where the plugin lives
+export AIRCANA_PLUGIN_ROOT="$PLUGIN_ROOT"
+
+echo "$(date): Starting knowledge base refresh from plugin root: $PLUGIN_ROOT" >> "$LOG_FILE"
+
+# Find all knowledge bases in agents directory
+AGENTS_DIR="${PLUGIN_ROOT}/agents"
+
+if [ ! -d "$AGENTS_DIR" ]; then
+    echo "$(date): No agents directory found, skipping refresh" >> "$LOG_FILE"
+    echo "{}"
+    exit 0
+fi
+
+# Track if we refreshed any KBs
+REFRESHED_COUNT=0
+SKIPPED_COUNT=0
+
+# Iterate through each KB directory
+for kb_dir in "${AGENTS_DIR}"/*/ ; do
+    # Skip if no directories found
+    [ -d "$kb_dir" ] || continue
+
+    kb_name=$(basename "$kb_dir")
+    manifest_file="${kb_dir}manifest.json"
+
+    # Skip if no manifest exists
+    if [ ! -f "$manifest_file" ]; then
+        echo "$(date): No manifest found for KB '$kb_name', skipping" >> "$LOG_FILE"
+        continue
+    fi
+
+    # Determine KB type from manifest (default to remote if not specified)
+    kb_type="remote"
+
+    # Try to parse with jq if available, otherwise use grep
+    if command -v jq >/dev/null 2>&1; then
+        kb_type=$(jq -r '.kb_type // "remote"' "$manifest_file" 2>/dev/null || echo "remote")
+    else
+        # Fallback: grep for kb_type field
+        if grep -q '"kb_type"[[:space:]]*:[[:space:]]*"local"' "$manifest_file" 2>/dev/null; then
+            kb_type="local"
+        fi
+    fi
+
+    # Only refresh remote KBs
+    if [ "$kb_type" = "local" ]; then
+        echo "$(date): Skipping local KB '$kb_name'" >> "$LOG_FILE"
+        SKIPPED_COUNT=$((SKIPPED_COUNT + 1))
+        continue
+    fi
+
+    # Refresh remote KB
+    echo "$(date): Refreshing remote KB '$kb_name'" >> "$LOG_FILE"
+    if aircana kb refresh "$kb_name" >> "$LOG_FILE" 2>&1; then
+        echo "$(date): Successfully refreshed KB '$kb_name'" >> "$LOG_FILE"
+        REFRESHED_COUNT=$((REFRESHED_COUNT + 1))
+    else
+        echo "$(date): Warning - Failed to refresh KB '$kb_name'" >> "$LOG_FILE"
+    fi
+done
+
+# Update timestamp on completion (even if some refreshes failed)
+date +%s > "$TIMESTAMP_FILE"
+
+# Log summary
+echo "$(date): KB refresh completed - refreshed: $REFRESHED_COUNT, skipped (local): $SKIPPED_COUNT" >> "$LOG_FILE"
+
+# Return success with context
+if [ $REFRESHED_COUNT -gt 0 ]; then
+    CONTEXT="Refreshed $REFRESHED_COUNT remote knowledge base(s)"
+else
+    CONTEXT="No remote knowledge bases to refresh"
+fi
+
+ESCAPED_CONTEXT=$(echo -n "$CONTEXT" | sed 's/"/\\"/g')
+cat << EOF
+{
+  "hookSpecificOutput": {
+    "hookEventName": "SessionStart",
+    "additionalContext": "$ESCAPED_CONTEXT"
+  }
+}
+EOF

data/lib/aircana/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Aircana
-  VERSION = "4.0.0.rc2"
+  VERSION = "4.0.0.rc3"
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: aircana
 version: !ruby/object:Gem::Version
-  version: 4.0.0.rc2
+  version: 4.0.0.rc3
 platform: ruby
 authors:
 - Weston Dransfield
 bindir: exe
 cert_chain: []
-date: 2025-10-17 00:00:00.000000000 Z
+date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: httparty
@@ -115,15 +115,8 @@ files:
 - README.md
 - Rakefile
 - SECURITY.md
-- commands/apply-feedback.md
-- commands/ask-expert.md
-- commands/execute.md
-- commands/plan.md
-- commands/record.md
-- commands/review.md
 - compose.yml
 - exe/aircana
-- hooks/hooks.json
 - lib/aircana.rb
 - lib/aircana/cli.rb
 - lib/aircana/cli/app.rb
@@ -132,7 +125,6 @@ files:
 - lib/aircana/cli/commands/doctor_helpers.rb
 - lib/aircana/cli/commands/dump_context.rb
 - lib/aircana/cli/commands/generate.rb
-- lib/aircana/cli/commands/hooks.rb
 - lib/aircana/cli/commands/init.rb
 - lib/aircana/cli/commands/kb.rb
 - lib/aircana/cli/commands/plugin.rb
@@ -177,6 +169,7 @@ files:
 - lib/aircana/templates/hooks/notification_sqs.erb
 - lib/aircana/templates/hooks/post_tool_use.erb
 - lib/aircana/templates/hooks/pre_tool_use.erb
+- lib/aircana/templates/hooks/refresh_skills.erb
 - lib/aircana/templates/hooks/rspec_test.erb
 - lib/aircana/templates/hooks/rubocop_pre_commit.erb
 - lib/aircana/templates/hooks/session_start.erb
@@ -207,7 +200,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.6.2
+rubygems_version: 3.6.9
 specification_version: 4
 summary: CLI for creating and managing Claude Code plugins with per-agent knowledge
   bases

data/commands/apply-feedback.md

@@ -1,15 +0,0 @@
-INSTRUCTIONS : Use the Task tool with subagent_type 'apply-feedback' to apply code review feedback from the previous /air-review command.
-
-Pass the review feedback from the conversation context to the apply-feedback agent.
-
-The apply-feedback agent will:
-1. Parse review feedback from the previous review
-2. Create todo list of changes prioritized by severity
-3. Present plan to user for approval
-4. Apply approved changes
-5. Re-run unit tests to verify changes
-6. Fix any test failures
-7. Amend the HEAD commit with improvements using 'git commit --amend --no-edit'
-8. Summarize changes made
-
-IMPORTANT: This command reads the review output from the conversation context, so it must be run in the same conversation as /air-review.

data/commands/ask-expert.md

@@ -1,42 +0,0 @@
-INSTRUCTIONS : You are coordinating expert consultation to answer a question by leveraging multiple specialized sub-agents. Follow this precise workflow:
-
-STEP 1: QUESTION VALIDATION
-Ask the user: \"What is your question?\" and wait for their response before proceeding.
-
-STEP 2: COORDINATION PHASE
-Use the Task tool with subagent_type 'sub-agent-coordinator' to analyze the question and identify relevant sub-agents. Provide the coordinator with the complete question context.
-
-STEP 3: PARALLEL EXPERT CONSULTATION
-Based on the coordinator's recommendations, use the Task tool to consult each identified relevant sub-agent in parallel. For each agent:
-- Use the appropriate subagent_type for each recommended agent
-- Provide the original question plus any agent-specific context the coordinator suggested
-- Execute multiple Task tool calls in a single message for parallel processing
-
-STEP 4: SYNTHESIS AND RESPONSE
-After receiving responses from all consulted agents:
-- Analyze and synthesize the expert feedback
-- Identify common themes, conflicting viewpoints, and complementary insights
-- Provide a comprehensive answer that leverages the collective expertise
-- Cite which agents contributed specific insights where relevant
-- Note any areas where experts disagreed and provide your assessment
-
-STEP 5: FOLLOW-UP GUIDANCE
-If the question requires further clarification or the expert responses suggest additional considerations:
-- Suggest specific follow-up questions
-- Recommend additional agents to consult if needed
-- Provide guidance on next steps based on the expert consensus
-
-IMPORTANT EXECUTION NOTES:
-- Always start with the sub-agent-coordinator for proper agent selection
-- Use parallel Task tool execution when consulting multiple agents (single message with multiple tool calls)
-- Ensure each agent receives context appropriate to their expertise domain
-- Synthesize responses rather than simply concatenating them
-- Maintain focus on providing actionable, comprehensive answers
-
-EXAMPLE PARALLEL EXECUTION:
-If coordinator recommends agents A, B, and C, send one message with three Task tool calls:
-1. Task(subagent_type='agent-A', prompt='[question + A-specific context]')
-2. Task(subagent_type='agent-B', prompt='[question + B-specific context]')
-3. Task(subagent_type='agent-C', prompt='[question + C-specific context]')
-
-This approach ensures you leverage the full expertise available while maintaining efficient coordination.

data/commands/execute.md

@@ -1,13 +0,0 @@
-INSTRUCTIONS : Use the Task tool with subagent_type 'executor' to execute the implementation plan from a Jira ticket.
-
-INSTRUCTIONS FOR EXECUTOR AGENT:
-Ask the user to provide a Jira ticket key/ID to execute.
-
-The executor agent will:
-1. Read the plan from the Jira ticket via the 'jira' sub-agent
-2. Review and validate the plan structure
-3. Create a detailed execution todo list in Claude Code planning mode
-4. Present the plan for your approval
-5. Execute the approved implementation tasks
-
-IMPORTANT: All Jira operations are delegated to the 'jira' sub-agent using Task tool with subagent_type 'jira'.

data/commands/plan.md

@@ -1,33 +0,0 @@
-INSTRUCTIONS : First, ask the user to specify relevant files, directories, or areas of the codebase to examine for this planning task.
-
-Then use the Task tool with subagent_type 'planner' to invoke the planner agent with the following explicit instructions:
-
-STEP 1: CREATE TODO LIST FILE
-First, create a todo list file with the following tasks enumerated in order:
-
-1. Ask user for relevant files and context (if not already provided)
-2. Use Task tool with subagent_type 'jira' to verify Jira ticket information (or ask user to create/provide ticket)
-3. Perform targeted initial research on user-specified files
-4. Consult relevant sub-agents with research context (run in parallel when possible)
-5. Create high-level strategic implementation plan
-6. Iterate with user feedback
-7. Suggest user runs '/air-record' command to save the plan to Jira ticket
-
-STEP 2: EXECUTE EACH TASK IN ORDER
-Work through each task in the todo list sequentially:
-- Mark each task as 'in_progress' when you start it
-- Mark each task as 'completed' when finished
-- Continue until all tasks are done
-
-IMPORTANT CONTEXT-SHARING PROTOCOL:
-- When consulting sub-agents, explicitly provide: files already searched, files already read, key findings, and specific focus area
-- This prevents sub-agents from duplicating research work
-
-IMPORTANT PLAN CONSTRAINTS:
-- Focus on strategic, high-level implementation guidance
-- NO rollout plans, effort estimates, or exhaustive code implementations
-- Small code examples (5-10 lines) are OK to illustrate concepts
-
-User specified relevant files/areas: [User will specify]
-
-Ask the user to provide a Jira ticket or task description.

data/commands/record.md

@@ -1,17 +0,0 @@
-INSTRUCTIONS : Use the Task tool with subagent_type 'jira' to append the implementation plan to the Jira ticket description using Jira MCP tools.
-
-INSTRUCTIONS FOR JIRA AGENT:
-1. Read the implementation plan from the current context (look for recent planning output)
-2. Get the current ticket description using mcp__jira__getJiraIssue with fields=["description"]
-3. Append the plan to the existing description under a new "## Implementation Plan" heading
-4. Update the ticket using mcp__jira__editJiraIssue with the combined description
-5. Format the appended plan section with:
-   - Consulted sub-agents
-   - Relevant files analyzed
-   - Planning timestamp
-   - Implementation steps as todo list using `[ ]` format
-6. Provide the ticket URL for easy access
-
-CRITICAL: The jira sub-agent must append to the ticket description using mcp__jira__editJiraIssue (NOT create files or comments).
-
-IMPORTANT: Delegate all Jira operations to the 'jira' sub-agent using Task tool with subagent_type 'jira'. The Jira ticket key/ID is already in context.

data/commands/review.md

@@ -1,12 +0,0 @@
-INSTRUCTIONS : Use the Task tool with subagent_type 'reviewer' to conduct an adversarial code review of the HEAD commit.
-
-The reviewer agent will:
-1. Get HEAD commit details and changes
-2. Analyze changed files to identify technical domains
-3. Use the sub-agent-coordinator to select relevant expert agents
-4. Present changes to experts in parallel for review
-5. Synthesize feedback organized by severity
-6. Store review output for the apply-feedback command
-7. Suggest running '/air-apply-feedback' to apply recommended changes
-
-IMPORTANT: The review agent will automatically review the HEAD commit. No arguments needed.

data/hooks/hooks.json

@@ -1,31 +0,0 @@
-{
-  "PostToolUse": [
-    {
-      "hooks": [
-        {
-          "type": "command",
-          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/post_tool_use.sh"
-        }
-      ]
-    }
-  ],
-  "PreToolUse": [
-    {
-      "hooks": [
-        {
-          "type": "command",
-          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/pre_tool_use.sh"
-        }
-      ]
-    },
-    {
-      "hooks": [
-        {
-          "type": "command",
-          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/rubocop_pre_commit.sh"
-        }
-      ],
-      "matcher": "Bash"
-    }
-  ]
-}