Does it support both Clojure and ClojureScript?

Yes, it is specifically configured to handle code reviews for both backend Clojure and frontend ClojureScript files.

Can I use it for projects that don't follow the Metabase style guide?

While optimized for Metabase standards, it also references the community Clojure style guide and general functional programming best practices applicable to any project.

What kind of feedback does it avoid?

The skill is tuned to avoid 'noise'—it won't post congratulatory comments for trivial changes or mention formatting issues like parentheses that are typically handled by linters.

Does this skill replace static analysis tools like clj-kondo?

No, it is designed to complement them. While clj-kondo catches syntax and basic errors, this skill focuses on semantic naming, architectural patterns, and style guide compliance.

Clojure Code Reviewer

Name: Clojure Code Reviewer
Author: Activer007

byActiver007

Collaboration Tools

Reviews Clojure and ClojureScript code for compliance with Metabase standards and functional programming best practices.

About

The Clojure Code Reviewer skill equips Claude with the expertise to evaluate Clojure and ClojureScript code against rigorous professional standards. It specifically monitors for naming conventions, such as the use of nouns for pure functions and exclamation marks for side effects, while enforcing structural rules like function length limits and proper module boundaries. By automating the detection of style violations and architectural inconsistencies, this skill allows developers to focus on logic and system design during the pull request process, ensuring a clean, maintainable, and idiomatic codebase.

Key Features

Enforces strict naming conventions including kebab-case and side-effect suffixes
Ensures REST API and Malli schema consistency across backend services
0 GitHub stars
Validates documentation standards for public variables and TODO formats
Audits test suite organization including parallel execution markers
Checks for code organization issues like function length and visibility scopes

Use Cases

Auditing legacy ClojureScript components for style guide compliance
Standardizing documentation and naming across large-scale functional projects
Automating peer reviews for Clojure-based pull requests

About

Key Features

Enforces strict naming conventions including kebab-case and side-effect suffixes
Ensures REST API and Malli schema consistency across backend services
0 GitHub stars
Validates documentation standards for public variables and TODO formats
Audits test suite organization including parallel execution markers
Checks for code organization issues like function length and visibility scopes

Use Cases

Auditing legacy ClojureScript components for style guide compliance
Standardizing documentation and naming across large-scale functional projects
Automating peer reviews for Clojure-based pull requests