LintLangGemini CLI #
Receive concise repair guidance after successful write_file and replace calls. The extension's AfterTool hook scans supported language-bearing files and adds findings to the tool result.
Setup #
Use a configured Gemini CLI and uv on PATH. Install the source revision recorded in the released integration guide:
gemini extensions install https://github.com/hermes-labs-ai/lintlang --ref=f89c3b0b8986fad162859dca052a8d5fe227eede
gemini extensions list
Review the installation consent prompt, then restart an active session. This recorded pair is LintLang 0.5.3 with Gemini CLI 0.32.1. It is intentionally separate from the current scanner release.
The extension includes the scanner source. Its runner uses an isolated uv environment with PyYAML==6.0.3; no separate LintLang installation is needed. A dependency cache miss can require a download.
Verify #
Confirm that gemini extensions list reports lintlang (0.5.3), enabled with Type: git and the source commit above. After restarting, inspect feedback from a successful write_file or replace on a supported file.
The hook covers .yaml, .yml, .json, .txt, .md, .prompt, and .py. It returns at most eight findings plus an omitted count, with a 30-second execution cap. Clean and unsupported files add no context.
Behavior and removal #
Feedback is advisory: the extension does not block or rewrite the file. It omits the raw evidence field, though other diagnostics may still include source-derived information. Newer host/scanner combinations need separate verification.
If feedback is absent, check the extension's enabled state, uv availability, and whether the edit succeeded. An ambient pip installation does not supply the bundled runner's dependencies.
gemini extensions disable lintlang
gemini extensions uninstall lintlang
Restart the host after disabling or removing the extension.