Agent skill · writing content · metabase
clojure-review
Review Clojure and ClojureScript code changes for compliance with Metabase coding standards, style violations, and code quality issues. Use when reviewing pull requests or diffs containing Clojure/ClojureScript code.
Why this skill is useful
Provides specific guidelines and checks for Clojure code compliance that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 48,568 stars on the source repository.
What this skill does
Clojure Code Review Skill @./../shared/clojure-style-guide.md @./../shared/clojure-commands.md Review guidelines What to flag: Check compliance with the Metabase Clojure style guide (included above) If CLOJURESTYLEGUIDE.adoc exists in the working directory, also check compliance with the community Clojure style guide Flag all style guide violations What NOT to post: Do not post comments congratulating someone for trivial changes or for following style guidelines Do not post comments confirming things "look good" or telling them they did something correctly Only post comments about style violations or potential issues Example bad code review comments to avoid: This TODO comment is properly formatted with author and date - nice work! Good addition of limit 1 to the query - this makes the test more efficient without changing its behavior. The kondo ignore comment is appropriately placed here Test name properly ends with -test as required by the style guide. Special cases: Do not post comments about missing parentheses (these will be caught by the linter) Quick review checklist Use this to scan through changes efficiently: Naming [ ] Descriptive names (no tbl, zs') [ ] Pure functions named as nouns describing their return value [ ] kebab-case for all variables and functions [ ] Side-effect functions end with ! [ ] No namespace-alias repetition in function names Documentation [ ] Public vars in src or enterprise/backend/src have useful docstrings [ ] Docstrings use Markdown conventions [ ] References use [[other-var]] not backticks [ ] TODO comments include author and date: ;; TODO (Name 2025-01-01) -- description Docstring content — check every new or rewritten docstring against the anti-pattern table in the style guide above. Read the diff's docstrings on their own, separately from the code: prose is where review attention slides off, and a long docstring reads as diligence rather than as the liability it usually is. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills metabase/clojure-review