lint-check

Run code quality linters across Python, JavaScript, Go, Ruby, and Java projects.

21|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/mehdic/bazinga --skill lint-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-check
Source: https://github.com/mehdic/bazinga/tree/main/.claude/skills/lint-check
Command: npx skills add https://github.com/mehdic/bazinga --skill lint-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ruff, pylint, eslint, golangci-lint, rubocop, checkstyle, pmd, and includes scripts (resource) components.

What problem does it solve?

Inconsistent code style, hidden bugs, and code smells can degrade codebase quality and slow down development. This Skill automatically enforces coding standards and best practices, reducing technical debt and improving maintainability, so you can focus on building features, not fixing formatting.

Core Features & Use Cases

  • Multi-Language Linting: Supports Python (ruff/pylint), JavaScript (eslint), Go (golangci-lint), Ruby (rubocop), and Java (Checkstyle/PMD).
  • Style & Quality Checks: Identifies style violations, code complexity, potential bugs, and anti-patterns.
  • Structured Reports: Provides clear reports with file, line, column, severity, rule, and message for easy remediation.
  • Use Case: Integrate this Skill into your CI/CD pipeline or trigger it during code reviews. It will automatically flag any code that doesn't meet project standards, allowing developers to fix issues before they merge, saving review time and preventing regressions.

Quick Start

To run a lint check on the current codebase: bash .claude/skills/lint-check/lint.sh

Frequently Asked Questions about lint-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run automated code quality checks across multiple programming languages?

Code quality linters automatically detect style violations, complexity issues, and best-practice violations across Python, JavaScript, Go, Ruby, and Java. This Skill runs ruff, pylint, eslint, golangci-lint, rubocop, and Checkstyle/PMD tools, generating structured JSON reports with file, line, column, severity, and rule details for each issue found.

Can I integrate linting into my CI/CD pipeline to catch code issues before merge?

Yes. This Skill is designed for code review gates and pre-merge checks. It detects style and quality violations during CI/CD workflows, flags non-compliant code automatically, and produces structured reports so developers can fix issues before merging, reducing review time and preventing regressions.

What languages and linting tools does this support?

This Skill supports Python (ruff, pylint), JavaScript (eslint), Go (golangci-lint), Ruby (rubocop), and Java (Checkstyle, PMD). It auto-detects the project language and applies the appropriate linter, saving results in JSON format for easy remediation and integration.

How are linting results formatted and where are they stored?

Linting results are saved as JSON to bazinga/artifacts/{SESSION_ID}/skills/lint_results.json with file path, line number, column, severity level, rule name, and message for each violation, enabling downstream processing and integration with other tools.

What happens if a linting tool isn't installed or times out?

This Skill includes graceful degradation and timeout handling. If a tool is unavailable or exceeds time limits, the Skill continues without that tool rather than failing entirely, ensuring partial results are still captured and reported.

Does this Skill help reduce technical debt and inconsistent code style?

Yes. By enforcing consistent coding standards and flagging code smells, complexity issues, and anti-patterns, this Skill reduces technical debt and improves maintainability across teams, allowing developers to focus on feature work rather than manual formatting and style fixes.