How does it handle API and Database code?

The skill includes specific rules for REST API naming (kebab-case vs snake_case), Malli schemas, and Toucan database logic patterns.

What standards does this Clojure skill follow?

It primarily follows the Metabase Clojure style guide and the community Clojure style guide, focusing on naming, structure, and documentation.

Why doesn't the skill give positive feedback?

The skill is optimized for efficiency and noise reduction; it only flags violations and issues to keep reviews actionable and concise.

Does it replace standard linters like clj-kondo?

No, it is designed to complement them. It specifically avoids flagging syntax issues like missing parentheses to focus on higher-level architectural and stylistic violations.

Clojure Review & Quality Guide

Name: Clojure Review & Quality Guide
Author: Microck

byMicrock

•

108

Collaboration Tools

Performs rigorous Clojure and ClojureScript code reviews following Metabase-style standards and functional programming best practices.

About

The clojure-review skill equips Claude with a specialized framework for auditing Clojure and ClojureScript code changes. It focuses on enforcing strict naming conventions, documentation standards, and architectural patterns common in large-scale Clojure applications. By identifying style violations, improper side-effect markers, and REST API inconsistencies, this skill ensures codebase maintainability while intentionally avoiding noise like congratulatory comments or linter-managed syntax issues. It is an essential tool for teams looking to automate high-level code quality checks during pull request reviews.

Key Features

Detailed REST API audit including Malli schema and route naming checks
108 GitHub stars
Strict enforcement of Metabase and community Clojure style guides
Analysis of code organization, function length, and namespace visibility
Naming convention validation for pure functions, side-effects, and variables
Verification of documentation standards and TODO formatting

Use Cases

Ensuring REST API endpoints follow specific naming and schema conventions
Automating the first pass of code reviews for Clojure pull requests
Enforcing consistent standards across teams moving from other languages to Clojure

About

Key Features

Detailed REST API audit including Malli schema and route naming checks
108 GitHub stars
Strict enforcement of Metabase and community Clojure style guides
Analysis of code organization, function length, and namespace visibility
Naming convention validation for pure functions, side-effects, and variables
Verification of documentation standards and TODO formatting

Use Cases

Ensuring REST API endpoints follow specific naming and schema conventions
Automating the first pass of code reviews for Clojure pull requests
Enforcing consistent standards across teams moving from other languages to Clojure