Skip to main content
command CX Codex

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

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add INDXDev/jevlint
/plugin install jevlint@jevlint
Open on GitHub

What 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@jevlint

2Manually: put the files in place

.claude/commands/explain.md

Call it with /explain. For all projects use ~/.claude/commands/

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.

explain SuperClaude-Org A command to explain code, system architecture, and concepts at the right level of depth. Helps you understand unfamiliar code or teach concepts to others. CX Codex +1 ★ 23,950repo stars cypress-explain cypress-io cypress-explain explains Cypress E2E and component tests, clarifies API commands, and reviews test specifications without modifying any files. CX Codex +1 8,900installs ast-grep dgageot The ast-grep MCP server for Claude Code provides syntax-aware code search, linting, and expression rewrites through abstract syntax trees. It is used for precise codebase refactoring. CX Codex +1 no-comments backnotprop no-comments is a Claude Code skill that launches a subagent to strip stale comments and convert text constraints into automated tests or lint rules. CX Codex +1 10,400installs printing-press-polish mvanhorn printing-press-polish runs diagnostics on generated CLIs, fixes test failures automatically, and prepares them to publish. Useful when verify pass rate drops below 80% or scorecard falls under 85. CX Codex +1 7,200installs optimize-plugin FradSer optimize-plugin validates Claude plugin structure, runs Python sanity checks, and fixes issues via a subagent. Useful when auditing or refactoring plugin manifests and components. CX Codex +1 117installs ai_slop_reviewer ZaxbyHub ai_slop_reviewer audits codebases for empty stubs, hallucinated dependencies, testing theater, and LLM-generated structural flaws before production release. CX Codex +1 ★ 539repo stars

From the same set5

Project sponsors

Companies that keep this analytics open