VS Code extension

PragyaLint for Visual Studio Code brings dead-code diagnostics into the editor. It runs pragyalint --json on your workspace and publishes findings to the Problems panel, colored by confidence, then lets you preview and apply fixes without leaving the editor.

Install

code --install-extension IndianCoder3.sks-pragyalint

Or open the Extensions panel (Ctrl+Shift+X) and search for PragyaLint.

marketplace.visualstudio.com/…IndianCoder3.sks-pragyalint

Requirements

The extension shells out to the pragyalint CLI, so it must be installed and reachable — install the CLI with pip install pragyalint or pipx first. If the process that launches VS Code can't see it on its PATH, set pragyalint.binaryPath to the absolute path (see settings and ENOENT troubleshooting).

Commands

Command	What it does
`PragyaLint: Scan workspace`	Runs `pragyalint --json` and reports dead code into the Problems panel.
`PragyaLint: Preview fixes (dry-run)`	Runs `--fix --dry-run` and opens the plan in a read-only document.
`PragyaLint: Apply safe fixes`	Applies high-confidence fixes.
`PragyaLint: Scan and remove dead code (all confidence)`	Full prune: `--fix --confidence low+ --force`.

Problems are colored by confidence — error (high), warning (medium), info (low) — matching the CLI report.

Settings

Setting	Default	Description
`pragyalint.binaryPath`	`pragyalint`	Executable to run. Set to an absolute path when the CLI isn't on the editor's `PATH`.
`pragyalint.confidence`	`high`	Minimum confidence for fixes (`high`, `medium+`, `low+`, `all`).
`pragyalint.showLowConfidence`	`true`	Show or hide low-confidence findings in the Problems panel.

Troubleshooting

ENOENT / "cannot find pragyalint" — the CLI isn't on the environment's PATH. Find it with which pragyalint (Windows: where pragyalint) and set pragyalint.binaryPath.
Wrong interpreter — install the CLI into the same virtualenv VS Code's Python interpreter is using.
Stale results — re-run Scan workspace; nothing is cached between runs.

Full diagnosis guidance: Errors & troubleshooting.