@tdsoft-tech/aikit 0.1.15 → 0.1.17

package/.githooks/pre-commit

@@ -0,0 +1,70 @@
+#!/bin/sh
+#
+# bd (beads) pre-commit hook
+#
+# This hook ensures that any pending bd issue changes are flushed to
+# .beads/issues.jsonl before the commit is created, preventing a
+# race condition where daemon auto-flush fires after the commit.
+#
+
+# Check if bd is available
+if ! command -v bd >/dev/null 2>&1; then
+  echo "Warning: bd command not found, skipping pre-commit flush" >&2
+  exit 0
+fi
+
+# Check if we're in a bd workspace
+# For worktrees, .beads is in the main repository root, not the worktree
+BEADS_DIR=""
+if git rev-parse --git-dir >/dev/null 2>&1; then
+  # Check if we're in a worktree
+  if [ "$(git rev-parse --git-dir)" != "$(git rev-parse --git-common-dir)" ]; then
+    # Worktree: .beads is in main repo root
+    MAIN_REPO_ROOT="$(git rev-parse --git-common-dir)"
+    MAIN_REPO_ROOT="$(dirname "$MAIN_REPO_ROOT")"
+    if [ -d "$MAIN_REPO_ROOT/.beads" ]; then
+      BEADS_DIR="$MAIN_REPO_ROOT/.beads"
+    fi
+  else
+    # Regular repo: check current directory
+    if [ -d .beads ]; then
+      BEADS_DIR=".beads"
+    fi
+  fi
+fi
+
+if [ -z "$BEADS_DIR" ]; then
+  # Not a bd workspace, nothing to do
+  exit 0
+fi
+
+# Check if bd is actually initialized (has beads.db or config.yaml)
+# This prevents errors if .beads/ exists but bd was never initialized
+if [ ! -f "$BEADS_DIR/beads.db" ] && [ ! -f "$BEADS_DIR/config.yaml" ]; then
+  # .beads/ exists but bd is not initialized, skip bd operations
+  exit 0
+fi
+
+# Flush pending changes to JSONL
+# Use --flush-only to skip git operations (we're already in a git hook)
+# Suppress output unless there's an error
+if ! bd sync --flush-only >/dev/null 2>&1; then
+  echo "Error: Failed to flush bd changes to JSONL" >&2
+  echo "Run 'bd sync --flush-only' manually to diagnose" >&2
+  exit 1
+fi
+
+# If the JSONL file was modified, stage it
+# For worktrees, JSONL is in the main repo's working tree, not the worktree,
+# so we can't use git add. Skip this step for worktrees.
+if [ -f "$BEADS_DIR/issues.jsonl" ]; then
+  if [ "$(git rev-parse --git-dir)" = "$(git rev-parse --git-common-dir)" ]; then
+    # Regular repo: file is in the working tree, safe to add
+    git add "$BEADS_DIR/issues.jsonl" 2>/dev/null || true
+  fi
+  # For worktrees: .beads is in the main repo's working tree, not this worktree
+  # Git rejects adding files outside the worktree, so we skip it.
+  # The main repo will see the changes on the next pull/sync.
+fi
+
+exit 0

package/dist/cli.js

@@ -1227,6 +1227,64 @@ bd init
           return false;
         }
       }
+      /**
+       * Setup git hooks for Beads integration
+       */
+      async setupGitHooks() {
+        try {
+          const gitHooksDir = join9(this.projectPath, ".git", "hooks");
+          const preCommitHook = join9(gitHooksDir, "pre-commit");
+          const hookContent = `#!/bin/sh
+#
+# bd (beads) pre-commit hook
+#
+# This hook ensures that any pending bd issue changes are flushed to
+# .beads/issues.jsonl before the commit is created, preventing a
+# race condition where daemon auto-flush fires after the commit.
+#
+
+# Check if bd is available
+if ! command -v bd >/dev/null 2>&1; then
+  echo "Warning: bd command not found, skipping pre-commit flush" >&2
+  exit 0
+fi
+
+# Check if we're in a bd workspace
+BEADS_DIR=""
+if [ -d ".beads" ]; then
+  BEADS_DIR=".beads"
+fi
+
+if [ -z "$BEADS_DIR" ]; then
+  # Not a bd workspace, nothing to do
+  exit 0
+fi
+
+# Check if bd is actually initialized (has beads.db or config.yaml)
+# This prevents errors if .beads/ exists but bd was never initialized
+if [ ! -f "$BEADS_DIR/beads.db" ] && [ ! -f "$BEADS_DIR/config.yaml" ]; then
+  # .beads/ exists but bd is not initialized, skip bd operations
+  exit 0
+fi
+
+# Flush pending changes to JSONL
+# Use --flush-only to skip git operations (we're already in a git hook)
+# Suppress output unless there's an error
+if ! bd sync --flush-only >/dev/null 2>&1; then
+  echo "Error: Failed to flush bd changes to JSONL" >&2
+  echo "Run 'bd sync --flush-only' manually to diagnose" >&2
+  exit 1
+fi
+
+exit 0
+`;
+          await writeFile5(preCommitHook, hookContent, { mode: 493 });
+          return true;
+        } catch (error) {
+          logger.error("Failed to setup git hooks:", error);
+          return false;
+        }
+      }
       /**
        * Get current status
        */
@@ -2361,9 +2419,7 @@ var DEFAULT_COMMANDS = [
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the task description with this command. Use it directly - do NOT ask the user for a task description!
-- The arguments contain the task description you should create
+Task description: $ARGUMENTS
 
 1. Create a new bead file with unique ID
 2. Add task description, status, and notes
@@ -2385,9 +2441,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the feature or task to plan. Use it directly - do NOT ask the user what to plan!
-- The arguments contain the feature/task description you should create a plan for
+Feature or task to plan: $ARGUMENTS
 
 1. UNDERSTAND: Clarify requirements through Socratic questioning
 2. RESEARCH: Check existing patterns and dependencies
@@ -2429,9 +2483,7 @@ Brief description of the goal.
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the task reference or description. Use it directly - do NOT ask the user which task to implement!
-- The arguments contain the task reference (e.g., task-001) or task description to implement
+Task reference or description: $ARGUMENTS
 
 1. LOAD: Get task details from .beads/ or plan
 2. TEST: Write failing tests first (RED)
@@ -2530,9 +2582,7 @@ Before marking complete:
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the task description. Use it directly - do NOT ask the user what task to perform!
-- The arguments contain the task description to execute
+Task description: $ARGUMENTS
 
 **Phase 1: Requirements Gathering**
 - Interactive selection of task type (Feature, Bug Fix, Refactoring, etc.)
@@ -2622,9 +2672,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the issue description. Use it directly - do NOT ask user what to fix!
-- The arguments contain the issue description you should fix
+Issue description: $ARGUMENTS
 
 1. Identify issue
 2. Make minimal change to fix
@@ -2641,10 +2689,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided optional file argument. Use it if provided!
-- If a file argument is provided, focus on fixing types in that specific file
-- If no file argument is provided, fix all type errors in the project
+Optional file argument: $ARGUMENTS
 
 1. Run \`npm run typecheck\`
 2. Parse error output
@@ -2679,10 +2724,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided a commit message. Use it if provided!
-- If a commit message is provided, use that message directly
-- If no message is provided, generate a conventional commit message based on changes
+Optional commit message: $ARGUMENTS
 
 1. Stage changes: \`git add -A\`
 2. Generate commit message following conventional commits:
@@ -2704,10 +2746,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user may have pro
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided a PR title. Use it if provided!
-- If a title is provided, use that as the PR title
-- If no title is provided, generate a title based on changes
+Optional PR title: $ARGUMENTS
 
 1. Push current branch
 2. Generate PR description:
@@ -2728,9 +2767,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user may have pro
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the research topic. Use it directly - do NOT ask user what to research!
-- The arguments contain the topic you should research
+Research topic: $ARGUMENTS
 
 1. Search documentation and resources
 2. Find code examples and patterns
@@ -2770,10 +2807,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided a path. Use it if provided!
-- If a path is provided, review code in that specific directory
-- If no path is provided, review the entire codebase
+Optional path: $ARGUMENTS
 
 1. Check code quality metrics
 2. Identify:
@@ -2795,9 +2829,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user may have pro
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the feature to design. Use it directly - do NOT ask user what to design!
-- The arguments contain the feature you should design
+Feature to design: $ARGUMENTS
 
 1. Requirements gathering (Socratic questioning)
 2. Research existing solutions
@@ -2821,9 +2853,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided a problem. Use it directly - do NOT ask the user what to brainstorm about!
-- The arguments contain the problem you should brainstorm ideas for
+Problem to brainstorm: $ARGUMENTS
 
 1. Define problem clearly
 2. Generate diverse ideas (no judgement)
@@ -2842,9 +2872,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided the branch name. Use it directly - do NOT ask user what to name the branch!
-- The arguments contain the branch name to create
+Branch name: $ARGUMENTS
 
 1. Ensure clean working directory
 2. Pull latest main/master
@@ -2865,10 +2893,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided a target branch. Use it if provided!
-- If a target branch is provided, merge to that branch
-- If no target is provided, default to merging to main/master
+Optional target branch: $ARGUMENTS
 
 1. Run quality gates first
 2. Commit any pending changes
@@ -3061,10 +3086,7 @@ The analysis will be saved automatically for later reference.`
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided optional file or pattern argument. Use it if provided!
-- If a file/pattern argument is provided, focus refactoring on that specific target
-- If no argument is provided, identify refactoring opportunities across the codebase
+Optional file or pattern: $ARGUMENTS
 
 1. Ensure tests are in place
 2. Identify refactoring opportunities
@@ -3082,10 +3104,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user has provided optional pattern argument. Use it if provided!
-- If a pattern argument is provided, run tests matching that pattern
-- If no argument is provided, run the full test suite
+Optional pattern: $ARGUMENTS
 
 1. Run test command: \`npm run test\`
 2. Parse and display results
@@ -3103,10 +3122,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user has provided
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided --fix flag. Check for it!
-- If --fix flag is provided, automatically fix issues
-- If no --fix flag is provided, only report issues without fixing
+Optional flags: $ARGUMENTS
 
 1. Run linter: \`npm run lint\`
 2. Parse errors and warnings
@@ -3124,10 +3140,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user may have pro
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided an environment. Use it if provided!
-- If an environment is provided, deploy to that environment
-- If no environment is provided, default to production or prompt user
+Optional environment: $ARGUMENTS
 
 1. Run quality gates (test, lint, build)
 2. Check for uncommitted changes
@@ -3145,10 +3158,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user may have pro
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided a version. Use it if provided!
-- If a version is provided, rollback to that specific version
-- If no version is provided, list available versions and prompt user
+Optional version: $ARGUMENTS
 
 1. Identify current version
 2. List available versions
@@ -3166,11 +3176,7 @@ IMPORTANT: Look at the "Arguments Provided" section below. The user may have pro
 
 ## Workflow
 
-**Step 0: Use Provided Arguments**
-IMPORTANT: Look at the "Arguments Provided" section below. The user may have provided flags. Check for them!
-- If --tail N is provided, show only the last N lines
-- If --follow is provided, stream live log updates
-- If no flags are provided, show standard log output
+Optional flags: $ARGUMENTS
 
 1. Determine log location
 2. Apply filters if specified
@@ -3277,6 +3283,11 @@ Describe what this command does.
    * Format command for agent consumption
    */
   formatForAgent(command, args) {
+    let content = command.content;
+    if (args && args.trim()) {
+      const argParts = args.trim().split(/\s+/);
+      content = content.replace(/\$ARGUMENTS/g, args.trim()).replace(/\$1/g, argParts[0] || "").replace(/\$2/g, argParts[1] || "").replace(/\$3/g, argParts[2] || "").replace(/\$4/g, argParts[3] || "").replace(/\$5/g, argParts[4] || "");
+    }
     let output = `# Command: /${command.name}
 
 ## Usage
@@ -3289,14 +3300,11 @@ ${command.description}
 ${command.examples.map((e) => `- \`${e}\``).join("\n")}
 
 ## Workflow
-${command.content}
+${content}
 `;
     if (args && args.trim()) {
       output += `
-## Arguments Provided
-\`${args}\`
-
-**IMPORTANT**: The user provided these arguments with the command. Use them in the workflow as needed.
+User arguments are : ${args.trim()}
 `;
     }
     return output;
@@ -5417,6 +5425,9 @@ function registerInitCommand(program2) {
         } else {
           logger.info("Beads already initialized");
         }
+        logger.info("Setting up git hooks...");
+        await beads.setupGitHooks();
+        logger.success("\u2713 Git hooks configured");
         const opencodePath = paths.opencodeConfig();
         await installToOpenCode(opencodePath);
         console.log(chalk2.bold("\n\u2728 AIKit is ready!\n"));