KotlinSense — Claude Code Plugin
Kotlin code intelligence for Claude Code. Automatic type checking, import resolution, null safety detection, and error diagnostics injected directly into Claude's context after every .kt file edit.
What It Does
- Connects Claude Code to
kotlin-language-server via the Language Server Protocol
- After every
.kt / .kts file edit, diagnostics are injected into Claude's context automatically
- Claude sees type errors, missing imports, and null safety violations — and fixes them in the same turn
Works for any Kotlin or Android developer. No project-specific config needed — just install the binary and go.
Install
Step 1 — Add the marketplace
/plugin marketplace add SUDARSHANCHAUDHARI/KotlinSense
Step 2 — Install the plugin
/plugin install kotlinsense
Then install the language server binary:
/kotlinsense:install
Requires Java 17+. Run /kotlinsense:status to verify.
Commands
| Command | Description |
|---|
/kotlinsense:install | Download and install kotlin-language-server |
/kotlinsense:status | Check binary, Java, and LSP activation status |
/kotlinsense:navigate | Go-to-definition, find references, type inspection |
Quick Start
1. Install the language server
/kotlinsense:install
Downloads kotlin-language-server and adds it to your PATH. Requires Java 17+.
2. Verify it's working
/kotlinsense:status
Confirms the binary, Java, and LSP connection are all ready.
3. Open a Kotlin project and start editing
Open any .kt file and make an edit. KotlinSense automatically injects diagnostics into Claude's context — type errors, missing imports, null safety violations — and Claude fixes them in the same turn.
How It Works
Claude Code edits a .kt file
↓
kotlin-language-server analyzes the change (via LSP)
↓
Diagnostics injected into Claude's context
↓
Claude sees: "error: Unresolved reference 'foo' at MainActivity.kt:42"
↓
Claude fixes it immediately — same turn, no manual compile step
The LSP connection is defined in .lsp.json and activates automatically when the plugin is enabled.
Plugin Structure
KotlinSense/
├── .claude-plugin/
│ ├── plugin.json # Plugin manifest
│ └── marketplace.json # Marketplace manifest
├── .lsp.json # LSP server config (.kt / .kts → kotlin-language-server)
├── commands/ # /kotlinsense:install|status|navigate
├── scripts/
│ ├── install-kotlin-ls.sh # macOS / Linux installer
│ ├── install-kotlin-ls.ps1 # Windows PowerShell installer
│ └── verify-install.sh # Binary + Java environment check
├── skills/
│ ├── kotlinsense-usage/ # How the plugin works, known limitations
│ ├── kotlin-diagnostics/ # 10 common diagnostics with fixes
│ └── kotlin-android-patterns/ # Idiomatic ViewModel, StateFlow, Compose, Hilt patterns
├── README.md
├── CHANGELOG.md
└── LICENSE
Requirements
- Claude Code installed and authenticated
- Java 17+ (
java -version to check — install from adoptium.net)
- Internet connection for initial binary download (~50 MB)
Troubleshooting
Diagnostics not appearing after file edits
Run /kotlinsense:status to diagnose. Ensure kotlin-language-server is in PATH — restart terminal after install.
kotlin-language-server: command not found
Run /kotlinsense:install. Then check $HOME/.local/bin is in PATH: echo $PATH.
Slow startup (30–90 seconds on first open)
Normal — the server indexes the project on first open. Large Android projects take longer.
False positive errors on generated code (Room, Hilt, etc.)
Run ./gradlew build first so annotation processors generate their output, then reopen the file.
Java not found
Install Java 17+ from adoptium.net. Verify: java -version.
Documentation
For full details — complete command walkthroughs, diagnostics reference, first-time setup guide, troubleshooting, and plugin architecture — see DOCUMENTATION.md.
Author