Claudecode Linter

claudecode-linter

[](https://github.com/retif/claudecode-linter/actions/workflows/ci.yml) [](https://www.npmjs.com/package/claudecode-linter) [](https://github.com/retif/claudecode-linter/blob/main/LICENSE) [](https://socket.dev/npm/package/claudecode-linter)

Standalone linter for [Claude Code](https://docs.anthropic.com/en/docs/claude-code) plugins and configuration files.

Validates `plugin.json`, `SKILL.md`, agent/command markdown, `hooks.json`, `mcp.json`, `settings.json`, `CLAUDE.md`, `.lsp.json`, and `monitors/monitors.json` files. plugin.json, settings.json, the agent/skill/command frontmatter, .lsp.json and monitors.json are checked against JSON Schemas auto-extracted from Claude Code's runtime Zod validators — failures the linter reports are the same failures Claude Code would raise at session start.


Install

npm install -g claudecode-linter

Or run directly:

npx claudecode-linter ~/projects/my-plugin/

Or build it from a clone of this repository — there is no `dist/` until you build:

git clone https://github.com/retif/claudecode-linter
cd claudecode-linter
npm ci && npm run build      # install dependencies, compile to dist/
node dist/index.js path/to/plugin/

Commands elsewhere in this README are written as `claudecode-linter …` (the global / `npx` install); from a clone, that is `node dist/index.js …`.

Usage

Lint

Check plugin artifacts for errors without modifying files. This is the default mode — `--lint` is optional:

# Lint a plugin directory
claudecode-linter --lint path/to/plugin/
claudecode-linter path/to/plugin/  # same thing

# Lint multiple paths
claudecode-linter plugin-a/ plugin-b/