Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microck/clojure-review
Review Clojure and ClojureScript code changes for compliance with Metabase coding standards, style violations, and code quality issues.
Passed 22 of 23 test cases with the skill, and 15 of 23 without it.
and 6 more in the full report
8 fixed14 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
A pull request diff in `src/metabase/util.clj` contains a syntax issue with an unclosed parenthesis: ```clojure (defn format-name [x] (str/trim x ``` Should this unclosed parenthesis issue be posted as a PR review comment?
| Checked | Without skill | With skill |
|---|---|---|
| The output specifies omitting PR comments for missing parentheses caught by linters. | Missed | Passed |
The instructions your model reads when the skill loads.
@./../_shared/clojure-style-guide.md @./../_shared/clojure-commands.md
What to flag:
CLOJURE_STYLE_GUIDE.adoc exists in the working directory, also check compliance with the community Clojure style guideWhat NOT to post:
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:
Use this to scan through changes efficiently:
tbl, zs')test cases passed, vs 15 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.