Agent Plugins Marketplace
← All plugins

jev-lint

v0.4.1

Lint the things a linter cannot: names that drifted from their implementation, comments that became false, tests that do not verify what they claim. ast-grep picks the code, one sentence is the rule, a model answers it. Includes the shipped rule packs, a cookbook for writing your own, and the calibration procedure.

Claude Code1 Skill

By mizchiLicense: MIT46 GitHub starsUpdated 3 days ago

Directory evidence

Runtimes
Claude Code
Parsed components
1 skill or MCP entry
Source updated
Sep 21, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install jev-lint for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install jev-lint@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/mizchi/jev-lint

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.

Plugin files

jev-lint/
├── .claude-plugin/plugin.json
└── skills/jev-lint/SKILL.md

Included Skills1

jev-lintskills/jev-lint/SKILL.md

Use when running jev-lint, adding it to a repository or its CI, choosing which of its shipped rule packs to use, writing a new jev-lint rule (an ast-grep matcher plus one sentence a model judges), or calibrating a rule's cutoff. Triggers: `jev-lint`, `.jev-lint.yaml`, a `.jev-lint/rules/*.yml` or `rules/*.yml` file with `ask:` in it, questions like 'lint whether function names match their bodies' or 'find comments that are no longer true', and any request to check code for something a conventional linter cannot decide. Also use it before claiming a jev-lint rule 'works' — this skill defines what that requires.

Plugin manifests1

.claude-plugin/plugin.json
{
  "name": "jev-lint",
  "version": "0.4.1",
  "description": "Lint the things a linter cannot: names that drifted from their implementation, comments that became false, tests that do not verify what they claim. ast-grep picks the code, one sentence is the rule, a model answers it. Includes the shipped rule packs, a cookbook for writing your own, and the calibration procedure.",
  "author": {
    "name": "mizchi",
    "url": "https://github.com/mizchi"
  },
  "homepage": "https://github.com/mizchi/jev-lint",
  "repository": "https://github.com/mizchi/jev-lint",
  "license": "MIT",
  "keywords": [
    "lint",
    "ast-grep",
    "code-review",
    "naming",
    "comments",
    "commits",
    "typescript",
    "rust",
    "python",
    "go"
  ]
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[jev-lint on Agent Plugins Marketplace](https://pluginsmp.com/plugins/jev-lint)