explain · indxdev — Claude Code command: what it does, how to install
explain — a command for Claude Code that runs the jevlint tool against a single file. It reports every finding with its score and highlights what actually needs fixing.
MIT ★ 113 updated 2026-11-15
/plugin marketplace add INDXDev/jevlint
/plugin install jevlint@jevlintWhat explain does
The command runs jevlint diagnostics on a target file to report every issue and score. It walks through the findings, marks critical problems, and leaves harmless warnings alone. Project jevlint-score comments are kept intact without edits.
Execution relies on Bash calls to jevlint explain or jevlint audit. When an API key is configured, jevlint explain transmits file contents to the external provider, requiring user approval beforehand. To stay offline, the command executes jevlint audit <file> --ast-only --json and inspects ast.findings strictly on the local machine.
What it helps with
- inspect jevlint scores and warnings for an individual file
- distinguish actionable bugs from minor linter notices
- review file findings strictly offline via local AST data
- interpret linter diagnostics without altering score annotations
Example prompts for the agent
- /explain src/auth/session.ts
- Explain what jevlint thinks of controllers/user.py
- Run jevlint audit on lib/parser.js without sending data upstream
How to install explain
1Plugin marketplace
/plugin marketplace add INDXDev/jevlint/plugin install jevlint@jevlint2Manually: put the files in place
.claude/commands/explain.mdCall it with /explain. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/explain.mdCall it with /prompts:explain. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/explain.prompt.mdManually: put the files in place
.gemini/commands/explain.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about explain
How to install explain in Claude Code?
Run /plugin marketplace add INDXDev/jevlint and then /plugin install jevlint@jevlint. Alternatively, place the prompt file directly at .claude/commands/explain.md.
What does the explain command do?
It evaluates a specific file with jevlint, summarizes all detected findings, and points out which issues deserve developer attention.
Does explain send source code to external servers?
Running jevlint explain sends file content out if an API provider key is configured. To keep all data local, it falls back to jevlint audit <file> --ast-only --json.
Source text
explain.md · MIT
--- description: Show every finding and score for one file argument-hint: "<file>" allowed-tools: Bash(jevlint explain:*), Bash(jevlint audit:*) --- Explain what jevlint thinks of `$ARGUMENTS`. `jevlint explain` sends the file to the configured provider when a key is set, so ask before running it unless the user has already agreed. To stay on this machine, run `jevlint audit $ARGUMENTS --ast-only --json` and read the file's `ast.findings`. Say which findings matter and which you would leave alone. Do not add or change `jevlint-score` comments.
© INDX · MIT · INDXDev/jevlint
Similar slash commands
All slash commands for Code review and refactoring →explain by other authors comes first.