@link-assistant/hive-mind 0.47.1 → 0.48.0

package/CHANGELOG.md

@@ -1,5 +1,20 @@
 # @link-assistant/hive-mind
 
+## 0.48.0
+
+### Minor Changes
+
+- 93ea94b: Add solution drafts listing feature to hive command. When processing completes, hive now displays all completed issues with their linked pull requests before showing the "✅ All issues processed!" message.
+
+### Patch Changes
+
+- a44ab88: Add system prompt guidance to prefer using existing code as examples
+  - Added guideline to encourage searching for similar existing implementations before implementing from scratch
+  - Applied consistently across all three prompt modules (claude, codex, opencode)
+  - Helps maintain consistency with existing patterns and reduces redundant work
+
+- 1bdc96d: Fix --base-branch option to properly create branches from the specified base branch instead of from current HEAD
+
 ## 0.47.1
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@link-assistant/hive-mind",
-  "version": "0.47.1",
+  "version": "0.48.0",
   "description": "AI-powered issue solver and hive mind for collaborative problem solving",
   "main": "src/hive.mjs",
   "type": "module",

package/src/claude.prompts.lib.mjs

@@ -135,6 +135,7 @@ Initial research.
 
 Solution development and testing.
    - When issue is solvable, implement code with tests.
+   - When implementing features, search for similar existing implementations in the codebase and use them as examples instead of implementing everything from scratch.
    - When coding, each atomic step that can be useful by itself should be commited to the pull request's branch, meaning if work will be interrupted by any reason parts of solution will still be kept intact and safe in pull request.
    - When you test:
       start from testing of small functions using separate scripts;

package/src/codex.prompts.lib.mjs

@@ -127,6 +127,7 @@ Initial research.
 
 Solution development and testing.
    - When issue is solvable, implement code with tests.
+   - When implementing features, search for similar existing implementations in the codebase and use them as examples instead of implementing everything from scratch.
    - When coding, each atomic step that can be useful by itself should be commited to the pull request's branch, meaning if work will be interrupted by any reason parts of solution will still be kept intact and safe in pull request.
    - When you test:
       start from testing of small functions using separate scripts;

package/src/hive.mjs

@@ -108,6 +108,8 @@ if (isDirectExecution) {
     const { initializeSentry, withSentry, addBreadcrumb, reportError } = sentryLib;
     const graphqlLib = await import('./github.graphql.lib.mjs');
     const { tryFetchIssuesWithGraphQL } = graphqlLib;
+    const solutionDraftsLib = await import('./list-solution-drafts.lib.mjs');
+    const { listSolutionDrafts } = solutionDraftsLib;
     const commandName = process.argv[1] ? process.argv[1].split('/').pop() : '';
     const isLocalScript = commandName.endsWith('.mjs');
     const solveCommand = isLocalScript ? './solve.mjs' : 'solve';
@@ -196,9 +198,7 @@ if (isDirectExecution) {
             }
             // Add delay between repository requests
             await new Promise(resolve => setTimeout(resolve, 1000));
-
             const repoIssues = await fetchAllIssuesWithPagination(issueCmd);
-
             // Add repository information to each issue
             const issuesWithRepo = repoIssues.map(issue => ({
               ...issue,
@@ -207,10 +207,8 @@ if (isDirectExecution) {
                 owner: { login: ownerName },
               },
             }));
-
             collectedIssues.push(...issuesWithRepo);
             processedRepos++;
-
             if (issuesWithRepo.length > 0) {
               await log(`   ✅ Found ${issuesWithRepo.length} issues in ${ownerName}/${repoName}`, { verbose: true });
             }
@@ -1348,7 +1346,10 @@ if (isDirectExecution) {
             }
             Object.assign(stats, currentStats);
           }
-
+          // List completed issues with their solution draft PRs
+          if (stats.completed > 0) {
+            await listSolutionDrafts(issueQueue, log, batchCheckPullRequestsForIssues);
+          }
           await log('\n✅ All issues processed!');
           await log(`   Completed: ${stats.completed}`);
           await log(`   Failed: ${stats.failed}`);

package/src/list-solution-drafts.lib.mjs

@@ -0,0 +1,32 @@
+/**
+ * Solution Drafts Listing Module
+ * Displays completed issues with their linked pull requests
+ */
+
+/**
+ * Lists all completed issues with their solution drafts (PRs)
+ * @param {Object} issueQueue - The issue queue containing completed issues
+ * @param {Function} log - Logging function
+ * @param {Function} batchCheckPullRequestsForIssues - Function to batch check PRs for issues
+ */
+export async function listSolutionDrafts(issueQueue, log, batchCheckPullRequestsForIssues) {
+  if (!issueQueue.completed || issueQueue.completed.length === 0) return;
+  await log('\n📋 Issues with solution drafts:');
+  const byRepo = {};
+  for (const url of issueQueue.completed) {
+    const m = url.match(/github\.com\/([^/]+)\/([^/]+)\/issues\/(\d+)/);
+    if (m) (byRepo[`${m[1]}/${m[2]}`] ||= { owner: m[1], repo: m[2], iss: [] }).iss.push({ n: +m[3], url });
+  }
+  for (const r of Object.values(byRepo)) {
+    const prs = await batchCheckPullRequestsForIssues(
+      r.owner,
+      r.repo,
+      r.iss.map(i => i.n)
+    );
+    for (const i of r.iss)
+      if (prs[i.n]?.linkedPRs?.length) {
+        await log(`   - ${i.url}`);
+        for (const p of prs[i.n].linkedPRs) await log(`     → PR #${p.number}: ${p.url}`);
+      } else await log(`   - ${i.url} (no PR found)`);
+  }
+}

package/src/opencode.prompts.lib.mjs

@@ -119,6 +119,7 @@ Initial research.
 
 Solution development and testing.
    - When issue is solvable, implement code with tests.
+   - When implementing features, search for similar existing implementations in the codebase and use them as examples instead of implementing everything from scratch.
    - When coding, each atomic step that can be useful by itself should be commited to the pull request's branch, meaning if work will be interrupted by any reason parts of solution will still be kept intact and safe in pull request.
    - When you test:
       start from testing of small functions using separate scripts;

package/src/solve.branch.lib.mjs

@@ -115,11 +115,16 @@ export async function createOrCheckoutBranch({ isContinueMode, prBranch, issueNu
     // Traditional mode: create new branch for issue
     const randomHex = crypto.randomBytes(6).toString('hex');
     branchName = `issue-${issueNumber}-${randomHex}`;
-    await log(`\n${formatAligned('🌿', 'Creating branch:', `${branchName} from ${defaultBranch}`)}`);
+
+    // Use user-specified base branch if provided, otherwise use repository default
+    const baseBranch = argv.baseBranch || defaultBranch;
+    const branchSource = argv.baseBranch ? 'custom' : 'default';
+    await log(`\n${formatAligned('🌿', 'Creating branch:', `${branchName} from ${baseBranch} (${branchSource})`)}`);
 
     // IMPORTANT: Don't use 2>&1 here as it can interfere with exit codes
     // Git checkout -b outputs to stderr but that's normal
-    checkoutResult = await $({ cwd: tempDir })`git checkout -b ${branchName}`;
+    // Create branch from the specified base branch (origin/baseBranch)
+    checkoutResult = await $({ cwd: tempDir })`git checkout -b ${branchName} origin/${baseBranch}`;
   }
 
   if (checkoutResult.code !== 0) {