@orderful/droid 0.11.0 → 0.12.0

package/src/lib/tools.ts

@@ -4,6 +4,7 @@ import { fileURLToPath } from 'url';
 import YAML from 'yaml';
 import { loadConfig } from './config.js';
 import { type ToolManifest, type ToolIncludes, getPlatformTools } from './types.js';
+import { compareSemver } from './version.js';
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
 const BUNDLED_TOOLS_DIR = join(__dirname, '../tools');
@@ -112,29 +113,67 @@ export function getInstalledToolVersion(toolName: string): string | null {
   return null;
 }
 
-/**
- * Check if a tool has an update available
- */
-export function getToolUpdateStatus(toolName: string): {
+export interface ToolUpdateInfo {
+  name: string;
   hasUpdate: boolean;
   installedVersion: string | null;
   bundledVersion: string | null;
-} {
+}
+
+/**
+ * Check if a tool has an update available
+ */
+export function getToolUpdateStatus(toolName: string): ToolUpdateInfo {
   const installedVersion = getInstalledToolVersion(toolName);
   const tool = getBundledTools().find(t => t.name === toolName);
   const bundledVersion = tool?.version || null;
 
   if (!installedVersion || !bundledVersion) {
     return {
+      name: toolName,
       hasUpdate: false,
       installedVersion,
       bundledVersion,
     };
   }
 
+  // Use semver comparison: bundled > installed means update available
+  const hasUpdate = compareSemver(bundledVersion, installedVersion) > 0;
+
   return {
-    hasUpdate: bundledVersion !== installedVersion,
+    name: toolName,
+    hasUpdate,
     installedVersion,
     bundledVersion,
   };
 }
+
+/**
+ * Get all installed tools that have updates available
+ */
+export function getToolsWithUpdates(): ToolUpdateInfo[] {
+  const config = loadConfig();
+  const installedTools = getPlatformTools(config);
+  const bundledTools = getBundledTools();
+
+  const toolsWithUpdates: ToolUpdateInfo[] = [];
+
+  // Check each bundled tool to see if it's installed and has an update
+  for (const tool of bundledTools) {
+    // Find if any of the tool's required skills are installed
+    const requiredSkills = tool.includes.skills
+      .filter(s => s.required)
+      .map(s => s.name);
+
+    const isInstalled = requiredSkills.some(skillName => skillName in installedTools);
+
+    if (isInstalled) {
+      const updateStatus = getToolUpdateStatus(tool.name);
+      if (updateStatus.hasUpdate) {
+        toolsWithUpdates.push(updateStatus);
+      }
+    }
+  }
+
+  return toolsWithUpdates;
+}

package/src/lib/types.ts

@@ -42,12 +42,18 @@ export interface PlatformConfig {
   tools: Record<string, InstalledSkill>;
 }
 
+export interface AutoUpdateConfig {
+  app: boolean;   // Auto-update droid CLI (default: false)
+  tools: boolean; // Auto-update installed tools (default: true)
+}
+
 export interface DroidConfig {
   platform: Platform;
   user_mention: string;
   output_preference: OutputPreference;
   git_username: string;
   platforms: Record<string, PlatformConfig>;
+  auto_update?: AutoUpdateConfig;
 }
 
 // Legacy config structure for migration

package/src/tools/comments/TOOL.yaml

@@ -1,6 +1,6 @@
 name: comments
 description: "Enable inline conversations using @droid/@user markers. Tag @droid to ask the AI, AI responds with @{your-name}. Ideal for code review notes and async collaboration."
-version: 0.2.2
+version: 0.2.3
 status: beta
 
 includes:

package/src/tools/comments/skills/comments/SKILL.md

@@ -79,13 +79,22 @@ When you find a `@droid` marker:
 
 ### On `/comments check`:
 
+**Use a two-pass approach for coherent responses:**
+
+#### Pass 1: Read & Analyse
 1. **Read config first:** Check `~/.droid/skills/comments/overrides.yaml` for `preserve_comments` setting (default: `true`)
-2. Search for `> @droid` (and any configured `ai_mentions`) in the specified scope
+2. Search for ALL `> @droid` comments (and any configured `ai_mentions`) in the specified scope
 3. If there's a `git diff`, check those files first for relevant context
-4. For each comment, determine intent:
+4. **Read all comments before responding** - understand the full picture
+5. Look for connections between comments (one may inform another)
+6. Note any contradictions or tensions to address
+
+#### Pass 2: Respond & Write
+1. For each comment, determine intent:
    - **Action request** ("do X", "add Y", "fix Z") → Execute the action
    - **Question** ("what do you think", "should we") → Respond with `> @{user_mention}`
-5. **Handle original comment based on `preserve_comments`:**
+2. Ensure responses are coherent across all comments (don't contradict yourself)
+3. **Handle original comment based on `preserve_comments`:**
    - If `preserve_comments: true` → Keep the original `@droid` comment (add response below it)
    - If `preserve_comments: false` → Remove the original comment after addressing
 

package/src/tools/comments/skills/comments/SKILL.yaml

@@ -1,6 +1,6 @@
 name: comments
 description: "Enable inline conversations using @droid/@user markers. Tag @droid to ask the AI, AI responds with @{your-name}. Use /comments check to address markers, /comments cleanup to remove resolved threads. Ideal for code review notes and async collaboration."
-version: 0.2.2
+version: 0.2.3
 status: beta
 dependencies: []
 provides_output: false