codeseeker 1.7.2 → 1.7.3

package/README.md

@@ -34,9 +34,10 @@ Restart your IDE and you're done!
 
 **Linux (Snap) - All Distributions:**
 ```bash
-sudo snap install codeseeker --classic
+sudo snap install codeseeker
 codeseeker install --vscode      # or --cursor, --windsurf
 ```
+> ⚠️ **Snap limitation:** Due to strict confinement, the snap can only access projects in your home directory (`~/`). For projects outside `~/`, use npm or Homebrew instead.
 
 **macOS/Linux (Homebrew):**
 ```bash
@@ -454,6 +455,10 @@ Open an issue: [GitHub Issues](https://github.com/jghiringhelli/codeseeker/issue
 
 > **Note:** Claude Code and GitHub Copilot both run in VS Code and share the same MCP configuration (`.vscode/mcp.json`). The flags `--vscode`, `--claude-code`, and `--copilot` are interchangeable.
 
+## Support
+
+If CodeSeeker is useful to you, consider [sponsoring the project](https://github.com/sponsors/jghiringhelli).
+
 ## License
 
 MIT License. See [LICENSE](LICENSE).

package/dist/cli/commands/handlers/setup-command-handler.js

@@ -228,15 +228,15 @@ class SetupCommandHandler extends base_command_handler_1.BaseCommandHandler {
             try {
                 // Delete all nodes and relationships related to this project path
                 // This is a simplified approach for MVP
-                const result = await session.run(`
-          MATCH (n {projectPath: $projectPath})-[r*0..]->(m)
-          DETACH DELETE n, m
+                const result = await session.run(`
+          MATCH (n {projectPath: $projectPath})-[r*0..]->(m)
+          DETACH DELETE n, m
         `, { projectPath });
                 // Also clean up any orphaned relationships
-                await session.run(`
-          MATCH ()-[r]-()
-          WHERE r.projectPath = $projectPath
-          DELETE r
+                await session.run(`
+          MATCH ()-[r]-()
+          WHERE r.projectPath = $projectPath
+          DELETE r
         `, { projectPath });
                 console.log(theme_1.Theme.colors.success('✅ Cleaned up Neo4j knowledge graph data'));
             }
@@ -592,9 +592,9 @@ class SetupCommandHandler extends base_command_handler_1.BaseCommandHandler {
             const client = await pool.connect();
             try {
                 // Check if semantic_search_embeddings has the content_type column
-                const embeddingsSchemaCheck = await client.query(`
-          SELECT column_name FROM information_schema.columns
-          WHERE table_name = 'semantic_search_embeddings' AND column_name = 'content_type'
+                const embeddingsSchemaCheck = await client.query(`
+          SELECT column_name FROM information_schema.columns
+          WHERE table_name = 'semantic_search_embeddings' AND column_name = 'content_type'
         `);
                 if (embeddingsSchemaCheck.rows.length > 0) {
                     console.log(theme_1.Theme.colors.success('✅ Consolidated schema already applied correctly'));
@@ -651,65 +651,65 @@ class SetupCommandHandler extends base_command_handler_1.BaseCommandHandler {
      */
     async createBasicTables(client) {
         // Create essential tables manually
-        const basicSchema = `
-      -- Enable extensions
-      CREATE EXTENSION IF NOT EXISTS "uuid-ossp";
-      CREATE EXTENSION IF NOT EXISTS vector;
-
-      -- Projects table
-      CREATE TABLE IF NOT EXISTS projects (
-        id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
-        project_path TEXT UNIQUE NOT NULL,
-        project_name TEXT NOT NULL,
-        project_type TEXT DEFAULT 'unknown',
-        languages JSONB DEFAULT '[]'::jsonb,
-        frameworks JSONB DEFAULT '[]'::jsonb,
-        total_files INTEGER DEFAULT 0,
-        total_lines INTEGER DEFAULT 0,
-        status TEXT DEFAULT 'active',
-        metadata JSONB DEFAULT '{}'::jsonb,
-        created_at TIMESTAMPTZ DEFAULT NOW(),
-        updated_at TIMESTAMPTZ DEFAULT NOW()
-      );
-
-      -- Analysis results table
-      CREATE TABLE IF NOT EXISTS analysis_results (
-        id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
-        project_id UUID REFERENCES projects(id) ON DELETE CASCADE,
-        file_path TEXT NOT NULL,
-        file_hash TEXT NOT NULL,
-        analysis_type TEXT NOT NULL,
-        analysis_subtype TEXT,
-        analysis_result JSONB NOT NULL,
-        confidence_score DECIMAL(3,2),
-        severity TEXT DEFAULT 'info',
-        status TEXT DEFAULT 'detected',
-        metadata JSONB DEFAULT '{}'::jsonb,
-        tags JSONB DEFAULT '[]'::jsonb,
-        created_at TIMESTAMPTZ DEFAULT NOW(),
-        updated_at TIMESTAMPTZ DEFAULT NOW()
-      );
-
-      -- Semantic search embeddings table
-      CREATE TABLE IF NOT EXISTS semantic_search_embeddings (
-        id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
-        project_id UUID REFERENCES projects(id) ON DELETE CASCADE,
-        file_path TEXT NOT NULL,
-        chunk_index INTEGER DEFAULT 0,
-        content_type TEXT DEFAULT 'code',
-        content_text TEXT NOT NULL,
-        content_hash TEXT NOT NULL,
-        embedding VECTOR(384),
-        metadata JSONB DEFAULT '{}'::jsonb,
-        created_at TIMESTAMPTZ DEFAULT NOW(),
-        updated_at TIMESTAMPTZ DEFAULT NOW(),
-        UNIQUE(project_id, file_path, chunk_index, content_hash)
-      );
-
-      -- Create indexes
-      CREATE INDEX IF NOT EXISTS idx_projects_path ON projects(project_path);
-      CREATE INDEX IF NOT EXISTS idx_analysis_project_type ON analysis_results(project_id, analysis_type);
-      CREATE INDEX IF NOT EXISTS idx_semantic_embeddings_project ON semantic_search_embeddings(project_id);
+        const basicSchema = `
+      -- Enable extensions
+      CREATE EXTENSION IF NOT EXISTS "uuid-ossp";
+      CREATE EXTENSION IF NOT EXISTS vector;
+
+      -- Projects table
+      CREATE TABLE IF NOT EXISTS projects (
+        id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
+        project_path TEXT UNIQUE NOT NULL,
+        project_name TEXT NOT NULL,
+        project_type TEXT DEFAULT 'unknown',
+        languages JSONB DEFAULT '[]'::jsonb,
+        frameworks JSONB DEFAULT '[]'::jsonb,
+        total_files INTEGER DEFAULT 0,
+        total_lines INTEGER DEFAULT 0,
+        status TEXT DEFAULT 'active',
+        metadata JSONB DEFAULT '{}'::jsonb,
+        created_at TIMESTAMPTZ DEFAULT NOW(),
+        updated_at TIMESTAMPTZ DEFAULT NOW()
+      );
+
+      -- Analysis results table
+      CREATE TABLE IF NOT EXISTS analysis_results (
+        id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
+        project_id UUID REFERENCES projects(id) ON DELETE CASCADE,
+        file_path TEXT NOT NULL,
+        file_hash TEXT NOT NULL,
+        analysis_type TEXT NOT NULL,
+        analysis_subtype TEXT,
+        analysis_result JSONB NOT NULL,
+        confidence_score DECIMAL(3,2),
+        severity TEXT DEFAULT 'info',
+        status TEXT DEFAULT 'detected',
+        metadata JSONB DEFAULT '{}'::jsonb,
+        tags JSONB DEFAULT '[]'::jsonb,
+        created_at TIMESTAMPTZ DEFAULT NOW(),
+        updated_at TIMESTAMPTZ DEFAULT NOW()
+      );
+
+      -- Semantic search embeddings table
+      CREATE TABLE IF NOT EXISTS semantic_search_embeddings (
+        id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
+        project_id UUID REFERENCES projects(id) ON DELETE CASCADE,
+        file_path TEXT NOT NULL,
+        chunk_index INTEGER DEFAULT 0,
+        content_type TEXT DEFAULT 'code',
+        content_text TEXT NOT NULL,
+        content_hash TEXT NOT NULL,
+        embedding VECTOR(384),
+        metadata JSONB DEFAULT '{}'::jsonb,
+        created_at TIMESTAMPTZ DEFAULT NOW(),
+        updated_at TIMESTAMPTZ DEFAULT NOW(),
+        UNIQUE(project_id, file_path, chunk_index, content_hash)
+      );
+
+      -- Create indexes
+      CREATE INDEX IF NOT EXISTS idx_projects_path ON projects(project_path);
+      CREATE INDEX IF NOT EXISTS idx_analysis_project_type ON analysis_results(project_id, analysis_type);
+      CREATE INDEX IF NOT EXISTS idx_semantic_embeddings_project ON semantic_search_embeddings(project_id);
     `;
         await client.query(basicSchema);
     }
@@ -765,14 +765,14 @@ class SetupCommandHandler extends base_command_handler_1.BaseCommandHandler {
             const client = await pool.connect();
             try {
                 // Insert or update project
-                const result = await client.query(`
-          INSERT INTO projects (id, project_path, project_name, status, metadata)
-          VALUES ($1, $2, $3, 'active', $4)
-          ON CONFLICT (project_path) DO UPDATE SET
-            project_name = EXCLUDED.project_name,
-            status = 'active',
-            updated_at = NOW()
-          RETURNING id, project_name, project_path
+                const result = await client.query(`
+          INSERT INTO projects (id, project_path, project_name, status, metadata)
+          VALUES ($1, $2, $3, 'active', $4)
+          ON CONFLICT (project_path) DO UPDATE SET
+            project_name = EXCLUDED.project_name,
+            status = 'active',
+            updated_at = NOW()
+          RETURNING id, project_name, project_path
         `, [projectId, projectPath, projectName, JSON.stringify({
                         initialized_at: new Date().toISOString(),
                         cli_version: '2.0.0'
@@ -854,46 +854,46 @@ class SetupCommandHandler extends base_command_handler_1.BaseCommandHandler {
             if (platforms.length > 0) {
                 console.log(theme_1.Theme.colors.success(`   Found ${platforms.length} platforms: ${platforms.map(p => p.name).join(', ')}`));
             }
-            const defaultInstructions = `# CODESEEKER.md - ${path.basename(projectPath)}
-
-This file provides instructions to CodeSeeker for analyzing and working with this project.
-
-## Project Overview
-
-**Project**: ${path.basename(projectPath)}
-**Type**: api_service
-**Description**: Your project description here
-**Languages**: JavaScript, TypeScript
-**Architecture**: Add your architecture pattern
-**Testing Strategy**: Unit + Integration Testing
-**Coding Standards**: ESLint/Prettier
-
-${platformsSection}
-## Development Guidelines
-
-### Architecture Principles
-- Follow SOLID principles consistently
-- Use dependency injection patterns
-- Maintain clear separation of concerns
-
-### Code Quality Standards
-- High Performance, High Reliability, Secure
-- Comprehensive error handling
-- Proper logging and monitoring
-
-### Important Files and Patterns
-- Add important file patterns here
-- Document coding conventions
-- List key dependencies and their purposes
-
-## CodeSeeker Instructions
-
-- Analyze code for SOLID principles violations
-- Focus on maintainability and scalability
-- Suggest improvements for performance and security
-- Help with refactoring and code organization
-
-Generated by CodeSeeker CLI v2.0.0
+            const defaultInstructions = `# CODESEEKER.md - ${path.basename(projectPath)}
+
+This file provides instructions to CodeSeeker for analyzing and working with this project.
+
+## Project Overview
+
+**Project**: ${path.basename(projectPath)}
+**Type**: api_service
+**Description**: Your project description here
+**Languages**: JavaScript, TypeScript
+**Architecture**: Add your architecture pattern
+**Testing Strategy**: Unit + Integration Testing
+**Coding Standards**: ESLint/Prettier
+
+${platformsSection}
+## Development Guidelines
+
+### Architecture Principles
+- Follow SOLID principles consistently
+- Use dependency injection patterns
+- Maintain clear separation of concerns
+
+### Code Quality Standards
+- High Performance, High Reliability, Secure
+- Comprehensive error handling
+- Proper logging and monitoring
+
+### Important Files and Patterns
+- Add important file patterns here
+- Document coding conventions
+- List key dependencies and their purposes
+
+## CodeSeeker Instructions
+
+- Analyze code for SOLID principles violations
+- Focus on maintainability and scalability
+- Suggest improvements for performance and security
+- Help with refactoring and code organization
+
+Generated by CodeSeeker CLI v2.0.0
 `;
             await fs.writeFile(instructionsPath, defaultInstructions);
             console.log(theme_1.Theme.colors.success('✅ Created CODESEEKER.md with platform detection'));
@@ -932,94 +932,94 @@ Generated by CodeSeeker CLI v2.0.0
      * Used for CLAUDE.md, AGENTS.md, .cursorrules, COPILOT.md, GEMINI.md, GROK.md, etc.
      * This tells AI assistants to prefer CodeSeeker MCP tools over grep/glob
      */
-    CODESEEKER_MCP_GUIDANCE = `
-## CodeSeeker MCP Tools - MANDATORY FOR CODE DISCOVERY
-
-**CRITICAL**: This project has CodeSeeker MCP tools available. You MUST use them as your PRIMARY method for code discovery, NOT grep/glob.
-
-### Auto-Initialization Check
-
-**BEFORE any code search**, verify the project is indexed:
-1. Call \`projects()\` to see indexed projects
-2. If this project is NOT listed, call \`index({path: "PROJECT_ROOT_PATH"})\` first
-3. If tools return "Not connected", the MCP server may need restart
-
-### When to Use CodeSeeker (DEFAULT)
-
-**ALWAYS use CodeSeeker for these queries:**
-- "Where is X handled?" → \`search("X handling logic")\`
-- "Find the auth/login/validation code" → \`search("authentication")\`
-- "How does Y work?" → \`search_and_read("Y implementation")\`
-- "What calls/imports Z?" → \`show_dependencies({filepath: "path/to/Z"})\`
-- "Show me the error handling" → \`search_and_read("error handling patterns")\`
-
-| Task | MUST Use | NOT This |
-|------|----------|----------|
-| Find code by meaning | \`search("authentication logic")\` | ❌ \`grep -r "auth"\` |
-| Search + read files | \`search_and_read("error handling")\` | ❌ \`grep\` then \`cat\` |
-| Show dependencies | \`show_dependencies({filepath})\` | ❌ Manual file reading |
-| Find patterns | \`standards({project})\` | ❌ Searching manually |
-| Understand a file | \`read_with_context({filepath})\` | ❌ Just Read alone |
-
-### When to Use grep/glob (EXCEPTIONS ONLY)
-
-Only fall back to grep/glob when:
-- Searching for **exact literal strings** (UUIDs, specific error codes, magic numbers)
-- Using **regex patterns** that semantic search can't handle
-- You **already know the exact file path**
-
-### Why CodeSeeker is Better
-
-\`\`\`
-❌ grep -r "error handling" src/
-   → Only finds literal text "error handling"
-
-✅ search("how errors are handled")
-   → Finds: try-catch blocks, .catch() callbacks, error responses,
-     validation errors, custom Error classes - even if they don't
-     contain the words "error handling"
-\`\`\`
-
-### Available MCP Tools
-
-| Tool | Purpose | When to Use |
-|------|---------|-------------|
-| \`search(query)\` | Semantic search | First choice for any "find X" query |
-| \`search_and_read(query)\` | Search + read combined | When you need file contents |
-| \`show_dependencies({filepath})\` | Dependency graph | "What uses this?", "What does this depend on?" |
-| \`read_with_context({filepath})\` | File + related code | Reading a file for the first time |
-| \`standards({project})\` | Project patterns | Before writing new code |
-| \`index({path})\` | Index a project | If project not indexed |
-| \`sync({changes})\` | Update index | After editing files |
-| \`projects()\` | Show indexed projects | Check if project is indexed |
-
-### Keep Index Updated
-
-After using Edit/Write tools, call:
-\`\`\`
-sync({changes: [{type: "modified", path: "path/to/file"}]})
-\`\`\`
-
-## Claude Code Best Practices (from 2000+ hours of expert usage)
-
-### Subagent Strategy for Complex Tasks
-- For multi-step or complex tasks, spawn subagents using the **main model** (not cheaper/smaller models) instead of cramming everything into one context
-- Pattern: "Orchestrator coordinates + focused subagents execute" >> "Single massive context"
-- Use subagents MORE than you think necessary, especially for large codebases
-- Each subagent gets fresh, focused context = better quality output
-
-### Context Hygiene - Prevent "Lost in the Middle"
-- Quality degrades as context grows - the "lost in the middle" problem is real
-- Use **double-escape (Esc Esc)** to time travel when context gets polluted with failed attempts
-- Compact strategically and intentionally, not automatically
-- When output quality drops, consider starting fresh rather than adding more context
-
-### Error Attribution Mindset
-- Issues in AI-generated code trace back to **prompting or context engineering**
-- When something fails, ask "what context was missing?" not "the AI is broken"
-- Log failures mentally: prompt → context → outcome. Patterns will emerge.
-- Better input = better output. Always.
-
+    CODESEEKER_MCP_GUIDANCE = `
+## CodeSeeker MCP Tools - MANDATORY FOR CODE DISCOVERY
+
+**CRITICAL**: This project has CodeSeeker MCP tools available. You MUST use them as your PRIMARY method for code discovery, NOT grep/glob.
+
+### Auto-Initialization Check
+
+**BEFORE any code search**, verify the project is indexed:
+1. Call \`projects()\` to see indexed projects
+2. If this project is NOT listed, call \`index({path: "PROJECT_ROOT_PATH"})\` first
+3. If tools return "Not connected", the MCP server may need restart
+
+### When to Use CodeSeeker (DEFAULT)
+
+**ALWAYS use CodeSeeker for these queries:**
+- "Where is X handled?" → \`search("X handling logic")\`
+- "Find the auth/login/validation code" → \`search("authentication")\`
+- "How does Y work?" → \`search_and_read("Y implementation")\`
+- "What calls/imports Z?" → \`show_dependencies({filepath: "path/to/Z"})\`
+- "Show me the error handling" → \`search_and_read("error handling patterns")\`
+
+| Task | MUST Use | NOT This |
+|------|----------|----------|
+| Find code by meaning | \`search("authentication logic")\` | ❌ \`grep -r "auth"\` |
+| Search + read files | \`search_and_read("error handling")\` | ❌ \`grep\` then \`cat\` |
+| Show dependencies | \`show_dependencies({filepath})\` | ❌ Manual file reading |
+| Find patterns | \`standards({project})\` | ❌ Searching manually |
+| Understand a file | \`read_with_context({filepath})\` | ❌ Just Read alone |
+
+### When to Use grep/glob (EXCEPTIONS ONLY)
+
+Only fall back to grep/glob when:
+- Searching for **exact literal strings** (UUIDs, specific error codes, magic numbers)
+- Using **regex patterns** that semantic search can't handle
+- You **already know the exact file path**
+
+### Why CodeSeeker is Better
+
+\`\`\`
+❌ grep -r "error handling" src/
+   → Only finds literal text "error handling"
+
+✅ search("how errors are handled")
+   → Finds: try-catch blocks, .catch() callbacks, error responses,
+     validation errors, custom Error classes - even if they don't
+     contain the words "error handling"
+\`\`\`
+
+### Available MCP Tools
+
+| Tool | Purpose | When to Use |
+|------|---------|-------------|
+| \`search(query)\` | Semantic search | First choice for any "find X" query |
+| \`search_and_read(query)\` | Search + read combined | When you need file contents |
+| \`show_dependencies({filepath})\` | Dependency graph | "What uses this?", "What does this depend on?" |
+| \`read_with_context({filepath})\` | File + related code | Reading a file for the first time |
+| \`standards({project})\` | Project patterns | Before writing new code |
+| \`index({path})\` | Index a project | If project not indexed |
+| \`sync({changes})\` | Update index | After editing files |
+| \`projects()\` | Show indexed projects | Check if project is indexed |
+
+### Keep Index Updated
+
+After using Edit/Write tools, call:
+\`\`\`
+sync({changes: [{type: "modified", path: "path/to/file"}]})
+\`\`\`
+
+## Claude Code Best Practices (from 2000+ hours of expert usage)
+
+### Subagent Strategy for Complex Tasks
+- For multi-step or complex tasks, spawn subagents using the **main model** (not cheaper/smaller models) instead of cramming everything into one context
+- Pattern: "Orchestrator coordinates + focused subagents execute" >> "Single massive context"
+- Use subagents MORE than you think necessary, especially for large codebases
+- Each subagent gets fresh, focused context = better quality output
+
+### Context Hygiene - Prevent "Lost in the Middle"
+- Quality degrades as context grows - the "lost in the middle" problem is real
+- Use **double-escape (Esc Esc)** to time travel when context gets polluted with failed attempts
+- Compact strategically and intentionally, not automatically
+- When output quality drops, consider starting fresh rather than adding more context
+
+### Error Attribution Mindset
+- Issues in AI-generated code trace back to **prompting or context engineering**
+- When something fails, ask "what context was missing?" not "the AI is broken"
+- Log failures mentally: prompt → context → outcome. Patterns will emerge.
+- Better input = better output. Always.
+
 `;
     /**
      * Common agent instruction files to check and update with CodeSeeker MCP guidance

package/dist/cli/commands/services/context-aware-clarification-service.js

@@ -330,9 +330,9 @@ class ContextAwareClarificationService {
         const clarificationText = Array.from(clarifications.entries())
             .map(([id, answer]) => `- ${this.formatClarification(id, answer)}`)
             .join('\n');
-        return `${originalQuery}
-
-## User Clarifications (from codebase analysis):
+        return `${originalQuery}
+
+## User Clarifications (from codebase analysis):
 ${clarificationText}`;
     }
     /**

package/dist/cli/services/analysis/deduplication/code-consolidation-handler.js

@@ -190,47 +190,47 @@ class CodeConsolidationHandler {
      * Build comprehensive Claude Code instruction
      */
     buildClaudeInstruction(plan, projectPath) {
-        const instruction = `
-**Code Consolidation Task: ${plan.action.replace(/_/g, ' ').toUpperCase()}**
-
-**Objective**: ${plan.instructions}
-
-**Target Location**: ${plan.targetLocation}
-
-**Files to Modify**:
-${plan.affectedFiles.map(file => `- ${file}`).join('\n')}
-
-**Prerequisites** (complete these first):
-${plan.prerequisites.map(req => `- ${req}`).join('\n')}
-
-**Instructions**:
-1. Analyze the duplicate code patterns in the affected files
-2. Create the new utility/function/class at: ${plan.targetLocation}
-3. Replace all duplicate occurrences with calls to the new implementation
-4. Ensure all tests pass after refactoring
-5. Update any related documentation
-6. Follow the project's existing coding standards and patterns
-
-**Quality Requirements**:
-- Maintain or improve code readability
-- Ensure backward compatibility
-- Add appropriate error handling
-- Include comprehensive documentation
-- Follow SOLID principles
-- Ensure thread safety if applicable
-
-**Testing Requirements**:
-- Run all existing tests to ensure no regressions
-- Add tests for the new utility if creating new functionality
-- Verify performance is maintained or improved
-
-**Output Requirements**:
-- List all files modified
-- Report lines of code reduced
-- Summarize the consolidation approach taken
-- Note any potential issues or considerations for review
-
-Please proceed with this consolidation task step by step.
+        const instruction = `
+**Code Consolidation Task: ${plan.action.replace(/_/g, ' ').toUpperCase()}**
+
+**Objective**: ${plan.instructions}
+
+**Target Location**: ${plan.targetLocation}
+
+**Files to Modify**:
+${plan.affectedFiles.map(file => `- ${file}`).join('\n')}
+
+**Prerequisites** (complete these first):
+${plan.prerequisites.map(req => `- ${req}`).join('\n')}
+
+**Instructions**:
+1. Analyze the duplicate code patterns in the affected files
+2. Create the new utility/function/class at: ${plan.targetLocation}
+3. Replace all duplicate occurrences with calls to the new implementation
+4. Ensure all tests pass after refactoring
+5. Update any related documentation
+6. Follow the project's existing coding standards and patterns
+
+**Quality Requirements**:
+- Maintain or improve code readability
+- Ensure backward compatibility
+- Add appropriate error handling
+- Include comprehensive documentation
+- Follow SOLID principles
+- Ensure thread safety if applicable
+
+**Testing Requirements**:
+- Run all existing tests to ensure no regressions
+- Add tests for the new utility if creating new functionality
+- Verify performance is maintained or improved
+
+**Output Requirements**:
+- List all files modified
+- Report lines of code reduced
+- Summarize the consolidation approach taken
+- Note any potential issues or considerations for review
+
+Please proceed with this consolidation task step by step.
 `;
         return instruction.trim();
     }