x-lint-code

Lints source code in six languages using their respective primary/secondary tools.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/edercnj/ia-dev-environment --skill x-lint-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x-lint-code
Source: https://github.com/edercnj/ia-dev-environment/tree/main/src/main/resources/claude/skills/x-lint-code
Command: npx skills add https://github.com/edercnj/ia-dev-environment --skill x-lint-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically runs a language-appropriate linter to enforce code quality and consistency before commits.

Core Features & Use Cases

  • Primary linting with language-specific tools (e.g., checkstyle/spotbugs/pmd for Java, ktlint/detekt for Kotlin, eslint for TypeScript, ruff/pylint for Python, golangci-lint for Go, clippy for Rust).
  • Supports auto-fix modes and changed-only scope to speed up iterative development.
  • Integrates with pre-commit workflows to catch issues early in the development process.

Quick Start

Run the slash command /x-lint-code to lint your project with the appropriate linter.

Frequently Asked Questions about x-lint-code

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

FAQPage Schema
How do I run a pre-commit lint check on multiple programming languages?

Pre-commit lint checks across Java, Kotlin, TypeScript, Python, Go, and Rust are handled by automatically detecting the project language and running the appropriate linter. The tool aggregates results from primary and secondary linters to enforce code quality before commits.

What is the best way to auto-fix linting errors before committing code?

Auto-fixing linting errors before committing is done using the --fix mode. This automatically applies corrections from the language-specific linter, ensuring code quality and consistency without manual intervention during the pre-commit workflow.

Can I lint only the changed files to speed up my CI pipeline?

Linting only changed files is supported through the --changed-only scope mode. This speeds up iterative development and CI pipelines by restricting static analysis to modified source code rather than scanning the entire project.

Does this linter support static analysis for Go and Rust projects?

Static analysis for Go and Rust projects is fully supported using golangci-lint and clippy respectively. It runs these primary linters during the pre-commit phase to catch issues early in the development process.

How do I enforce strict code quality rules in a pre-commit hook?

Enforcing strict code quality rules is possible using the --strict mode during pre-commit linting. This elevates the static analysis sensitivity, ensuring that all primary and secondary linter violations are categorized and reported before code is committed.