# lintconfig

lintconfig turns a written coding standard into a linter configuration and runs your code against it. Breaks down rule text, maps it to Checkstyle settings, and proposes fixes for violations it finds.

- plugin · `type=plugin` · Claude Code · ★ 8 repo stars
- Author: idiomaticrefactoring
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/idiomaticrefactoring/LintConfig
- Updated: 2026-02-15
- Security check: automated, 2026-11-16 (text and 2 script files) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/plugins/lintconfig

## What it does

LintConfig takes a coding standard written in plain language and splits it into separate rules following a formal grammar. Each rule gets matched to specific linter settings, and the resulting config is checked for validity before use.

For every match, the plugin reports how closely the linter rule covers the original requirement: an exact fit, a broader condition, or a narrower one. From there it can run the linter against that config and return repair suggestions for the violations found, covering the full path from standard text to code fixes.

Only Checkstyle for Java is active right now; other linters are listed as planned. Preparing the rule knowledge base calls for Python 3.x, and the search tool in Claude Code needs `ripgrep` installed.

## Install

### Claude Code (native platform)

**Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add anthropics/claude-plugins-community
```
In the agent chat (not a shell):
```text
/plugin install lintconfig@claude-community
```

## When to use it
- turn a written coding standard into formal, atomic rules
- build and validate a Checkstyle configuration from those rules
- check how well a linter config matches the original standard
- run a linter against code and collect violations
- get fix suggestions for violations found during linting

## Example prompts
- Build a Checkstyle rule for package declarations that must not wrap across lines
- Lint ArrayCombination.java against our coding standard and suggest fixes
- Set up Checkstyle to match the Google Java Style Guide

## Similar
- [golang-lint](https://affpapa.org/en/nevibecode/skills/golang-lint.md) — skill · 42700 installs
- [dart-run-static-analysis](https://affpapa.org/en/nevibecode/skills/dart-run-static-analysis.md) — skill · 21200 installs
- [ruff-linting](https://affpapa.org/en/nevibecode/skills/ruff-linting.md) — skill · 529 installs
- [install-anti-slop](https://affpapa.org/en/nevibecode/skills/install-anti-slop.md) — skill · 16300 installs
- [skill-quality-reviewer](https://affpapa.org/en/nevibecode/skills/skill-quality-reviewer.md) — skill · 467 installs
- [sonarqube](https://affpapa.org/en/nevibecode/plugins/sonarqube.md) — plugin · ★ 116 repo stars

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
