gimme-the-lint
TheGlitchKing v2.8.1
Progressive linting system that only blocks on new violations, never on legacy code. Baselines existing lint issues by directory, then enforces clean code going forward. Supports Python (Ruff) and ...
From the developer
License
MIT
Works with
Claude Code
Description
From the marketplace listing
Progressive linting system that only blocks on new violations, never on legacy code. Baselines existing lint issues by directory, then enforces clean code going forward. Supports Python (Ruff) and JavaScript/TypeScript (ESLint) in monorepo configurations. Includes drift detection, auto-healing, git hooks, and a GitHub Action for CI enforcement. Directory-chunked baselines allow gradual adoption without a big-bang cleanup.
What changed
No changes recorded yet. Follow this plugin to keep track of future changes.
Similar plugins
Find competitors to follow as you develop your plugin.
-
A development harness for Claude Code that enforces disciplined workflows — decisions before code, tasks before implementation. Includes ...
Shared terms: enforce, code, block, detection
-
Self-maintaining system toolkit for Claude Code 4 commands: /daily (patrol scheduler), /disk-clean (current directory cleanup), /security...
Shared terms: clean, directory, system, code
-
Enforce engineering standards and code quality policies with zero-deferral code review. Finds and immediately fixes security issues, styl...
Shared terms: enforce, issue, violation, code
-
Interviews you about your coding preferences, analyzes your actual codebase, and generates personalized coding standards that Claude Code...
Shared terms: enforce, lint, code, python
-
Drop this plugin into any project and ask Claude to "review my architecture." It scans for clean architecture violations, SOLID breaches,...
Shared terms: clean, violation, code, monorepo
Keywords
Files & skills
gimme-the-lint · catalog manifest
Saved declaration
{}
gimme-the-lint · catalog manifest
Saved declaration
{
"name": "gimme-the-lint",
"source": {
"sha": "345323bcd853a3989c8a04fb774beb8c80422d27",
"url": "https://github.com/TheGlitchKing/gimme-the-lint.git",
"source": "url"
},
"homepage": "https://github.com/TheGlitchKing/gimme-the-lint",
"description": "Progressive linting system that only blocks on new violations, never on legacy code. Baselines existing lint issues by directory, then enforces clean code going forward. Supports Python (Ruff) and JavaScript/TypeScript (ESLint) in monorepo configurations. Includes drift detection, auto-healing, git hooks, and a GitHub Action for CI enforcement. Directory-chunked baselines allow gradual adoption without a big-bang cleanup."
}
gimme-the-lint · catalog manifest
Saved declaration
{
"name": "gimme-the-lint",
"author": {
"name": "TheGlitchKing",
"email": "theglitchking@users.noreply.github.com"
},
"license": "MIT",
"version": "2.8.1",
"homepage": "https://github.com/TheGlitchKing/gimme-the-lint",
"keywords": [
"linting",
"progressive-linting",
"polyglot",
"monorepo",
"git-hooks",
"drift-detection",
"eslint",
"ruff",
"golangci-lint",
"clippy",
"tflint",
"terraform",
"ansible-lint"
],
"repository": "https://github.com/TheGlitchKing/gimme-the-lint",
"description": "Polyglot progressive linting AND entity-contract checking — does your data model agree with the schemas that expose it? ESLint, Biome, Ruff, golangci-lint, Clippy, tflint, ansible-lint, squawk, buf, spectral, tsc, mypy, plus SQLAlchemy/Pydantic contract drift."
}
plugin.json observed Nov 6, 2026 · 10:44 UTC. Manifest source ↗
Catalog declarations and available plugin.json metadata are saved. Referenced skills and executable source files are not downloaded or tested. Missing components in a manifest do not prove that the plugin has none.
Installation instructions
Community
/plugin marketplace add anthropics/claude-plugins-community
/plugin install gimme-the-lint@claude-communityTechnical details
- Sources
- Community
- First seen
- Oct 3, 2026 · 22:13 UTC
- Last seen
- Nov 9, 2026 · 00:00 UTC
- Latest observed change
- Oct 3, 2026 · 22:13 UTC
- Collection status
- Listed
- Reported installs
- Not provided
Installation counts are source-reported, not independently verified active users. Observation dates are not release dates.
Download plugin data (JSON)Plugin history: freshly prepared. Prepared . Refreshed when catalog data changes or after 6 hours. Your account and Follow status are live.