Add precommit

rockerBOO · rockerBOO · commit bed0bd10d195 · 2025-07-18T19:29:25.000-04:00
diff --git a/.gitignore b/.gitignore
@@ -3,6 +3,7 @@
 
 # But not these files...
 !/.gitignore
+!/.pre-commit-config.yaml
 
 !*.go
 !go.sum
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
@@ -0,0 +1,45 @@
+# See https://pre-commit.com for more information
+repos:
+  # Built-in hooks
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.6.0
+    hooks:
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
+      - id: check-yaml
+      - id: check-added-large-files
+      - id: check-case-conflict
+      - id: check-merge-conflict
+      - id: check-json
+
+  # Go-specific hooks - using TekWizely (maintained alternative)
+  - repo: https://github.com/TekWizely/pre-commit-golang
+    rev: v1.0.0-rc.1
+    hooks:
+      # Go formatting (gofmt is built into Go)
+      - id: go-fmt
+
+      # Go vet (static analysis) - using repo-based to avoid package context issues
+      - id: go-vet-repo-mod
+
+      # Go mod tidy
+      - id: go-mod-tidy-repo
+
+      # Go build
+      - id: go-build-repo-mod
+
+      # Go tests
+      - id: go-test-repo-mod
+
+      # Comprehensive linting with golangci-lint (includes import formatting)
+      - id: golangci-lint-repo-mod
+        args: [--timeout=5m]
+
+# Exclude patterns
+exclude: |
+  (?x)^(
+      \.git/|
+      vendor/|
+      .*\.pb\.go$|
+      .*_generated\.go$
+  )$
diff --git a/Makefile b/Makefile
@@ -59,7 +59,7 @@ test-mcp-memory:
 .PHONY: security-scan gosec
 security-scan: gosec nancy
 
-gosec: 
+gosec:
 	docker run --rm -w /mcp-lsp-bridge/ -v $$(pwd):/mcp-lsp-bridge securego/gosec /mcp-lsp-bridge/...
 nancy:
 	go list -json -deps ./... | docker run --rm -i sonatypecommunity/nancy:latest sleuth
@@ -93,22 +93,22 @@ vet:
 build-all: clean
 	@echo "Building for multiple platforms..."
 	@mkdir -p $(DIST_DIR)
-	
+
 	# Linux amd64
 	GOOS=linux GOARCH=amd64 go build -o $(DIST_DIR)/$(BINARY_NAME)-linux-amd64 -ldflags "-X main.version=$(VERSION)" .
-	
+
 	# Linux arm64
 	GOOS=linux GOARCH=arm64 go build -o $(DIST_DIR)/$(BINARY_NAME)-linux-arm64 -ldflags "-X main.version=$(VERSION)" .
-	
+
 	# macOS amd64
 	GOOS=darwin GOARCH=amd64 go build -o $(DIST_DIR)/$(BINARY_NAME)-darwin-amd64 -ldflags "-X main.version=$(VERSION)" .
-	
+
 	# macOS arm64
 	GOOS=darwin GOARCH=arm64 go build -o $(DIST_DIR)/$(BINARY_NAME)-darwin-arm64 -ldflags "-X main.version=$(VERSION)" .
-	
+
 	# Windows amd64
 	GOOS=windows GOARCH=amd64 go build -o $(DIST_DIR)/$(BINARY_NAME)-windows-amd64.exe -ldflags "-X main.version=$(VERSION)" .
-	
+
 	# Windows arm64
 	GOOS=windows GOARCH=arm64 go build -o $(DIST_DIR)/$(BINARY_NAME)-windows-arm64.exe -ldflags "-X main.version=$(VERSION)" .
 
@@ -117,15 +117,15 @@ build-all: clean
 dist: build-all
 	@echo "Creating distribution packages..."
 	@mkdir -p $(DIST_DIR)/packages
-	
+
 	# Create tar.gz for Linux and macOS
 	for binary in $(DIST_DIR)/$(BINARY_NAME)-linux-* $(DIST_DIR)/$(BINARY_NAME)-darwin-*; do \
 		if [ -f "$$binary" ]; then \
 			basename=$$(basename $$binary); \
 			tar -czf $(DIST_DIR)/packages/$$basename.tar.gz -C $(DIST_DIR) $$basename; \
 		fi \
 	done
-	
+
 	# Create zip for Windows
 	for binary in $(DIST_DIR)/$(BINARY_NAME)-windows-*.exe; do \
 		if [ -f "$$binary" ]; then \
diff --git a/docs/README.md b/docs/README.md
@@ -51,4 +51,4 @@ When adding new tool documentation:
 1. Add detailed guides to `tools/`
 2. Update `tools/tools-reference.md` with basic info
 3. Update this README if adding new categories
-4. Link from relevant overview documents
+4. Link from relevant overview documents
diff --git a/docs/analysis-overview.md b/docs/analysis-overview.md
@@ -8,7 +8,7 @@ Quick overview of the main analysis and exploration tools in MCP-LSP Bridge.
 The most powerful analysis tool with 9 different analysis types:
 
 - **File Analysis**: Complexity metrics, code quality, recommendations
-- **Pattern Analysis**: Error handling, naming conventions, architecture patterns  
+- **Pattern Analysis**: Error handling, naming conventions, architecture patterns
 - **Workspace Analysis**: Project-wide overview and health metrics
 - **Symbol Analysis**: References, definitions, relationships
 - **Text Search**: Find patterns across codebase
@@ -72,4 +72,4 @@ Smart symbol search with context-aware filtering:
 - **`format_document`**: Format code with preview/apply modes
 - **`rename`**: Safely rename symbols across codebase
 
-See [tools-reference.md](tools/tools-reference.md) for complete tool list.
+See [tools-reference.md](tools/tools-reference.md) for complete tool list.
diff --git a/docs/codebase-guide.md b/docs/codebase-guide.md
@@ -127,7 +127,7 @@ Comprehensive overview of the MCP-LSP Bridge codebase structure and functionalit
 
 ## 🔄 Key Data Flow
 
-1. **MCP Request** → `mcpserver/tools/*.go` 
+1. **MCP Request** → `mcpserver/tools/*.go`
 2. **Tool Processing** → `bridge/bridge.go`
 3. **LSP Communication** → `lsp/client.go`
 4. **Analysis (if needed)** → `analysis/engine.go`
diff --git a/docs/configuration.md b/docs/configuration.md
@@ -5,7 +5,7 @@
 A valid `lsp_config.json` file is required for the bridge to function. The bridge needs:
 
 - Language server definitions (gopls, pyright-langserver, etc.)
-- File extension to language mappings  
+- File extension to language mappings
 - LSP server connection parameters
 
 ## Command-Line Options
@@ -132,4 +132,4 @@ COPY lsp_config.json /home/user/.config/mcp-lsp-bridge/lsp_config.json
 
 # Set the command to run when the container starts
 CMD ["mcp-lsp-bridge"]
-```
+```
diff --git a/docs/tools/README.md b/docs/tools/README.md
@@ -16,7 +16,7 @@ Complete documentation for all MCP-LSP Bridge tools.
 - Symbol relationships and impact analysis
 - Complete examples and sample outputs
 
-**[symbol-exploration-guide.md](symbol-exploration-guide.md)** - Guide for the `symbol_explore` tool  
+**[symbol-exploration-guide.md](symbol-exploration-guide.md)** - Guide for the `symbol_explore` tool
 - Intelligent symbol search
 - Context-aware filtering
 - Progressive detail levels
@@ -33,7 +33,7 @@ New to the tools? Start here:
 ## 🏗️ Tool Categories
 
 - **Analysis & Discovery**: `project_analysis`, `symbol_explore`, `get_range_content`, `analyze_code`
-- **Language Detection**: `detect_project_languages`, `infer_language`  
+- **Language Detection**: `detect_project_languages`, `infer_language`
 - **Connection Management**: `lsp_connect`, `lsp_disconnect`
 - **Code Intelligence**: `hover`, `signature_help`, `semantic_tokens`, `workspace_diagnostics`
 - **Safe Refactoring**: `code_actions`, `format_document`, `rename` (with preview/apply modes)
@@ -43,4 +43,4 @@ New to the tools? Start here:
 ## 📚 Other Documentation
 
 - **[../configuration.md](../configuration.md)** - Setup and configuration
-- **[../README.md](../../README.md)** - Main project documentation
+- **[../README.md](../../README.md)** - Main project documentation
diff --git a/docs/tools/project-analysis-guide.md b/docs/tools/project-analysis-guide.md
@@ -331,4 +331,4 @@ The analysis automatically detects and works with multiple programming languages
 Example with Python file:
 ```bash
 ● project_analysis (MCP)(analysis_type: "file_analysis", query: "scripts/test_mcp_tools.py")
-```
+```
diff --git a/docs/tools/symbol-exploration-guide.md b/docs/tools/symbol-exploration-guide.md
@@ -228,4 +228,4 @@ Finds symbols in test files or test directories.
 ● symbol_explore (MCP)(query: "Service", file_context: "service")
 ```
 
-The `symbol_explore` tool is designed to be your first stop when exploring unfamiliar codebases or when you need to quickly locate and understand symbols across your project.
+The `symbol_explore` tool is designed to be your first stop when exploring unfamiliar codebases or when you need to quickly locate and understand symbols across your project.
diff --git a/docs/tools/tools-reference.md b/docs/tools/tools-reference.md
@@ -120,4 +120,4 @@ This dual-mode operation ensures full control and visibility over automated code
 
 **Navigation**: `implementation`, `call_hierarchy`
 
-**System**: `mcp_lsp_diagnostics`
+**System**: `mcp_lsp_diagnostics`
diff --git a/lsp_config.example.json b/lsp_config.example.json
@@ -401,4 +401,4 @@
         ".sass": "css",
         ".less": "css"
     }
-}
+}
diff --git a/mcpserver/tools/project_analysis.go b/mcpserver/tools/project_analysis.go
@@ -31,7 +31,7 @@ func ProjectAnalysisTool(bridge interfaces.BridgeInterface) (mcp.Tool, server.To
 
 COMMON EXAMPLES:
 • Find functions/classes: analysis_type="workspace_symbols", query="calculateTotal"
-• Explore file structure: analysis_type="document_symbols", query="src/utils.py"  
+• Explore file structure: analysis_type="document_symbols", query="src/utils.py"
 • Find symbol usage: analysis_type="references", query="UserModel"
 • Find definition: analysis_type="definitions", query="processPayment"
 • Search text: analysis_type="text_search", query="TODO: fix"
@@ -44,7 +44,7 @@ ANALYSIS TYPES:
 • workspace_symbols: Find symbols across project
 • document_symbols: List symbols in specific file
 • references: Find all symbol usages
-• definitions: Locate symbol definitions  
+• definitions: Locate symbol definitions
 • text_search: Search project text
 • workspace_analysis: Comprehensive workspace analysis with language distribution, complexity metrics, and architectural health
 • symbol_relationships: Analyze symbol dependencies, usage patterns, and impact
diff --git a/scripts/README.md b/scripts/README.md
@@ -128,4 +128,4 @@ When adding new tests:
 1. Follow the existing test pattern
 2. Add appropriate error handling
 3. Update this README
-4. Ensure cross-platform compatibility
+4. Ensure cross-platform compatibility
diff --git a/scripts/memory_test.py b/scripts/memory_test.py
diff --git a/scripts/performance_test.py b/scripts/performance_test.py
diff --git a/scripts/test_mcp_tools.py b/scripts/test_mcp_tools.py
