# Review Clojure Style in Metabase Changes

Clojure pull requests can miss project-specific style and architecture rules. This skill gives Claude, Codex, and Claude Code a focused Metabase review checklist.

## Install

```bash
npx skillstore add metabase/clojure-review
```

## Metadata

- Status: approved
- Slug: metabase-clojure-review
- Skillstore revision: r1
- Version status: missing
- Tree hash: 21b0a31f3fa1e9fb8d64020213df20bfd40ed41e5728049acf17aaae3e25bef1
- Author: metabase
- GitHub username: metabase
- License: MIT
- Repository: https://github.com/metabase/metabase/tree/master/.claude/skills/clojure-review
- Ref: 1ffa7643651792ccb4bd3b15d924d2c97edff755
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/metabase-clojure-review
- Manifest: https://skillstore.pages.dev/api/skills/metabase-clojure-review/manifest

## Capabilities

- Reviews Clojure and ClojureScript diffs for Metabase naming conventions.
- Checks public vars, docstrings, TODO format, and private function markers.
- Flags test organization issues such as test naming and parallel test metadata.
- Checks module, REST API, MBQL, database, and driver convention rules.
- Provides concise review comment examples for style violations.

## Use Cases

- Review a Metabase backend pull request: Find style, module, API, and database convention issues before merge.
- Check ClojureScript naming and tests: Scan frontend-related ClojureScript changes for naming, test structure, and documentation concerns.
- Prepare contributor feedback: Generate focused review comments that explain violations without praising correct code.

## Prompt Templates

### Review a small diff

```
Review this Clojure diff with the clojure-review skill. Flag only Metabase style or quality issues that need action.
```

### Check API conventions

```
Review these Clojure API changes. Focus on route naming, schemas, query parameter casing, side effects, and test coverage.
```

### Audit database and MBQL code

```
Review this Metabase data-layer change. Focus on Toucan usage, MBQL boundaries, table naming, and efficient selects.
```

### Perform a full Metabase Clojure review

```
Review the full Clojure and ClojureScript pull request. Apply the checklist across naming, docs, tests, modules, APIs, MBQL, database, and drivers.
```

## Limitations

- It is tailored to Metabase conventions, not general Clojure style only.
- It relies on visible diffs and files provided to the agent.
- It does not replace clj-kondo, tests, or compiler checks.
- It should not post positive comments when no issue exists.

## Best Practices

- Run this skill on focused diffs where Clojure or ClojureScript files changed.
- Pair the review with clj-kondo, tests, and normal build checks.
- Post only actionable comments about violations or potential issues.

## Anti Patterns

- Do not use it to praise code that already follows the style guide.
- Do not treat it as a substitute for test execution or linting.
- Do not apply its Metabase-specific rules blindly to unrelated Clojure projects.

## Security Audit

- Audited at: 2026-07-09T04:13:17.301\+00:00
- Summary: The static findings are false positives caused by Markdown inline code, examples, and static local include references in SKILL.md. No prompt injection, malicious intent, data exfiltration, command execution, or unsafe filesystem behavior was found in the reviewed skill content.

## Stats

- Views: 351
- Downloads: 10
- Favorites: 1
- Popularity score: 0