clj-kondo

Lint Clojure code for syntax errors, style issues, and custom rules.

3|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/hugoduncan/library-skills --skill clj-kondo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clj-kondo
Source: https://github.com/hugoduncan/library-skills/tree/main/plugins/clojure-libraries/skills/clj-kondo
Command: npx skills add https://github.com/hugoduncan/library-skills --skill clj-kondo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill eliminates the slow, inconsistent, and error-prone nature of manual code review for Clojure, preventing technical debt and ensuring higher code quality.

Core Features & Use Cases

  • Automated Code Linting: Catches syntax errors, common mistakes, and enforces best practices across your Clojure codebase.
  • Custom Hooks: Define domain-specific linting rules to enforce unique project requirements and team conventions.
  • IDE & CI/CD Integration: Get real-time feedback in your editor and automate quality checks directly within your continuous integration pipeline.
  • Use Case: Automatically scan your entire Clojure codebase to identify unused bindings, unresolved symbols, and enforce team-specific naming conventions, ensuring consistent code quality across all pull requests.

Quick Start

Use the clj-kondo skill to lint all Clojure files in the 'src' and 'test' directories of my project.

Frequently Asked Questions about clj-kondo

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

FAQPage Schema
How do I lint Clojure code to catch syntax errors and style issues?

Clojure linting identifies syntax errors, style violations, and unused bindings by analyzing your code as a standalone binary. Run it against your source directories to get fast feedback on code quality without external dependencies.

Can I integrate linting into my CI/CD pipeline for Clojure projects?

Yes, clj-kondo runs directly in CI/CD workflows to automate code quality checks. It supports configurable output formats and fast execution, catching issues before they reach production without slowing your pipeline.

How do I enforce custom code rules specific to my Clojure team?

Custom hooks let you define domain-specific linting rules using the Hook API for analyze-call and macroexpand. This enables validation of project-specific conventions and naming standards across your codebase.

Does static analysis for Clojure work in my IDE?

Yes, clj-kondo integrates with IDEs to provide real-time linting feedback as you code. It delivers inline error detection and supports inline suppressions to manage false positives in your editor workflow.

What's the fastest way to scan large Clojure codebases for quality issues?

Clj-kondo runs as a fast native binary optimized for scanning entire projects. It processes both src and test directories efficiently while merging configuration rules, making it ideal for large-scale code quality analysis.

Can I suppress specific linting warnings in my Clojure code?

Inline suppressions allow you to disable linting checks for specific code sections, and configuration merging lets you customize which rules apply per project or directory, giving you granular control over enforcement.