java-functional-lsp 0.4.1__tar.gz → 0.4.2__tar.gz

java_functional_lsp-0.4.2/.githooks/pre-commit

@@ -0,0 +1,21 @@
+#!/usr/bin/env bash
+# Pre-commit: run lint, format check, type check, and tests.
+# Bypass with: git commit --no-verify
+
+set -e
+
+echo "Running pre-commit checks..."
+
+echo "  Lint..."
+uv run ruff check src/ tests/
+
+echo "  Format..."
+uv run ruff format --check src/ tests/
+
+echo "  Type check..."
+uv run mypy src/
+
+echo "  Tests..."
+uv run pytest -q
+
+echo "All checks passed."

java_functional_lsp-0.4.2/.githooks/pre-push

@@ -0,0 +1,19 @@
+#!/usr/bin/env bash
+# Prevent direct pushes to main/master — all changes must go through PRs.
+
+protected_branches=("main" "master")
+current_branch=$(git symbolic-ref --short HEAD 2>/dev/null)
+
+for branch in "${protected_branches[@]}"; do
+    if [ "$current_branch" = "$branch" ]; then
+        echo "ERROR: Direct push to '$branch' is not allowed."
+        echo "Create a feature branch and open a pull request instead."
+        echo ""
+        echo "  git checkout -b feat/my-change"
+        echo "  git push -u origin feat/my-change"
+        echo "  gh pr create"
+        echo ""
+        echo "To bypass (emergency only): git push --no-verify"
+        exit 1
+    fi
+done

{java_functional_lsp-0.4.1 → java_functional_lsp-0.4.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: java-functional-lsp
-Version: 0.4.1
+Version: 0.4.2
 Summary: Java LSP server enforcing functional programming best practices — null safety, immutability, no exceptions
 Project-URL: Homepage, https://github.com/aviadshiber/java-functional-lsp
 Project-URL: Repository, https://github.com/aviadshiber/java-functional-lsp
@@ -126,7 +126,7 @@ Add to `~/.claude/settings.json`:
 claude plugin add https://github.com/aviadshiber/java-functional-lsp.git
 ```
 
-This registers the LSP server, adds auto-install hooks, and provides the `/lint-java` command.
+This registers the LSP server, adds auto-install hooks, a PostToolUse hook that reminds Claude to fix violations on every `.java` file edit, and the `/lint-java` command.
 
 Or manually add to your Claude Code config:
 
@@ -141,12 +141,32 @@ Or manually add to your Claude Code config:
 }
 ```
 
-**Step 3: Nudge Claude to use diagnostics** (recommended):
+**Alternative: project-level `.lsp.json`** — instead of installing the plugin or editing global config, add a `.lsp.json` file at your project root:
 
-Add to your project's `CLAUDE.md`:
+```json
+{
+  "java-functional": {
+    "command": "java-functional-lsp",
+    "extensionToLanguage": { ".java": "java" }
+  }
+}
+```
+
+This is useful for CI environments, containers, or ensuring all team members get the LSP server without individual setup. The `java-functional-lsp` binary must still be installed (`pip install java-functional-lsp` or `brew install aviadshiber/tap/java-functional-lsp`).
+
+**Step 3: Nudge Claude to prefer LSP** (recommended):
+
+Add to `~/.claude/rules/code-intelligence.md`:
 ```markdown
-After writing or editing Java code, check LSP diagnostics before moving on.
-Fix any violations immediately — do not explain, just apply the fix.
+# Code Intelligence
+
+Prefer LSP over Grep/Glob/Read for code navigation:
+- goToDefinition / goToImplementation to jump to source
+- findReferences to see all usages across the codebase
+- hover for type info without reading the file
+
+After writing or editing code, check LSP diagnostics before
+moving on. Fix any type errors or missing imports immediately.
 ```
 
 **Troubleshooting:**
@@ -205,6 +225,7 @@ The server speaks the Language Server Protocol (LSP) via stdio, making it compat
 git clone https://github.com/aviadshiber/java-functional-lsp.git
 cd java-functional-lsp
 uv sync
+git config core.hooksPath .githooks
 
 # Run checks
 uv run ruff check src/ tests/
@@ -213,6 +234,10 @@ uv run mypy src/
 uv run pytest
 ```
 
+Git hooks in `.githooks/` enforce quality automatically:
+- **pre-commit** — runs lint, format, type check, and tests before each commit
+- **pre-push** — blocks direct pushes to main (use feature branches + PRs)
+
 See [CONTRIBUTING.md](CONTRIBUTING.md) for full guidelines.
 
 ## License

{java_functional_lsp-0.4.1 → java_functional_lsp-0.4.2}/README.md

@@ -98,7 +98,7 @@ Add to `~/.claude/settings.json`:
 claude plugin add https://github.com/aviadshiber/java-functional-lsp.git
 ```
 
-This registers the LSP server, adds auto-install hooks, and provides the `/lint-java` command.
+This registers the LSP server, adds auto-install hooks, a PostToolUse hook that reminds Claude to fix violations on every `.java` file edit, and the `/lint-java` command.
 
 Or manually add to your Claude Code config:
 
@@ -113,12 +113,32 @@ Or manually add to your Claude Code config:
 }
 ```
 
-**Step 3: Nudge Claude to use diagnostics** (recommended):
+**Alternative: project-level `.lsp.json`** — instead of installing the plugin or editing global config, add a `.lsp.json` file at your project root:
 
-Add to your project's `CLAUDE.md`:
+```json
+{
+  "java-functional": {
+    "command": "java-functional-lsp",
+    "extensionToLanguage": { ".java": "java" }
+  }
+}
+```
+
+This is useful for CI environments, containers, or ensuring all team members get the LSP server without individual setup. The `java-functional-lsp` binary must still be installed (`pip install java-functional-lsp` or `brew install aviadshiber/tap/java-functional-lsp`).
+
+**Step 3: Nudge Claude to prefer LSP** (recommended):
+
+Add to `~/.claude/rules/code-intelligence.md`:
 ```markdown
-After writing or editing Java code, check LSP diagnostics before moving on.
-Fix any violations immediately — do not explain, just apply the fix.
+# Code Intelligence
+
+Prefer LSP over Grep/Glob/Read for code navigation:
+- goToDefinition / goToImplementation to jump to source
+- findReferences to see all usages across the codebase
+- hover for type info without reading the file
+
+After writing or editing code, check LSP diagnostics before
+moving on. Fix any type errors or missing imports immediately.
 ```
 
 **Troubleshooting:**
@@ -177,6 +197,7 @@ The server speaks the Language Server Protocol (LSP) via stdio, making it compat
 git clone https://github.com/aviadshiber/java-functional-lsp.git
 cd java-functional-lsp
 uv sync
+git config core.hooksPath .githooks
 
 # Run checks
 uv run ruff check src/ tests/
@@ -185,6 +206,10 @@ uv run mypy src/
 uv run pytest
 ```
 
+Git hooks in `.githooks/` enforce quality automatically:
+- **pre-commit** — runs lint, format, type check, and tests before each commit
+- **pre-push** — blocks direct pushes to main (use feature branches + PRs)
+
 See [CONTRIBUTING.md](CONTRIBUTING.md) for full guidelines.
 
 ## License

{java_functional_lsp-0.4.1 → java_functional_lsp-0.4.2}/SKILL.md

@@ -59,6 +59,10 @@ Create `.java-functional-lsp.json` in your project root:
 - `throw-statement`/`catch-rethrow` auto-suppressed in `@Bean` methods
 - `mutable-dto` suggests `@ConstructorBinding` for `@ConfigurationProperties` classes
 
+## Automatic Enforcement
+
+The plugin includes a PostToolUse hook that fires on every Read/Edit/Write of `.java` files. If diagnostics appear, Claude is prompted to fix them immediately without explanation.
+
 ## On-Demand Linting
 
 Use `/lint-java <path>` to force-run the linter on specific files or directories.
@@ -81,6 +85,11 @@ LSP support requires `ENABLE_LSP_TOOL=1` in `~/.claude/settings.json`:
 { "env": { "ENABLE_LSP_TOOL": "1" } }
 ```
 
+For containers or CI, add a `.lsp.json` at the project root instead of installing the plugin:
+```json
+{ "java-functional": { "command": "java-functional-lsp", "extensionToLanguage": { ".java": "java" } } }
+```
+
 To nudge Claude to act on diagnostics, add to your project's `CLAUDE.md`:
 ```
 After writing or editing Java code, check LSP diagnostics before moving on.