malloy-review

Reviews Malloy semantic-model files against rubrics and emits a structured Markdown review report.

9|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/mathisdrn/orca --skill malloy-review-mathisdrn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: malloy-review
Source: https://github.com/mathisdrn/orca/tree/main/.agents/skills/malloy-review
Command: npx skills add https://github.com/mathisdrn/orca --skill malloy-review-mathisdrn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing Malloy semantic models by hand is slow and error-prone: silent cardinality bugs, non-unique primary keys, broken chart tags, and missing documentation all compile cleanly but produce wrong numbers or broken dashboards. This Skill automates a single-pass, rubric-driven audit of .malloy files and produces a navigable Markdown review file. ## Core Features & Use Cases - Rubric-based findings: Applies seven dimension rubrics (correctness, documentation, style, structure, queries, rendering, governance) with severity, confidence scoring, and suggested fixes, dropping findings below 80% confidence. - Data-verified checks: Uses execute_query to verify declared primary_key: uniqueness and search_malloy_docs to validate Malloy capabilities before flagging raw SQL. - Multiple review modes: Single-file mode, directory audit mode, and GitHub PR mode (--pr <n>) with optional --comment posting via gh pr comment. - Use Case: A data engineer opens a PR touching 14 Malloy model files. Run the review in PR mode to get a triage document with blockers, cross-cutting themes, per-file findings, and a machine-readable JSON tail. ## Quick Start Ask the assistant to review a Malloy file or folder, for example: run a Malloy code review on the models/finance directory and write the findings to a review file.

Frequently Asked Questions about malloy-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review Malloy model files for errors?▼

Invoke the review with a path to a `.malloy` file or directory, or use `--pr <n>` to review files changed in a GitHub PR. The skill resolves scope, applies rubrics across correctness, docs, style, structure, queries, rendering, and governance, then writes a Markdown review file.

What kinds of Malloy bugs does a code review catch?▼

It catches silently-wrong behavior the compiler misses: declared primary keys that are not unique in the data, unsafe division without nullif, string aggregates without casts, multi-aggregate chart views, unsupported render tags, and missing `#(doc)` documentation on public fields.

Can I review Malloy changes in a GitHub pull request?▼

Yes. Pass `--pr <n>` to fetch the PR diff, filter to changed `.malloy` files, and run the full workflow on the PR head. Add `--comment` to post the review back to the PR via `gh pr comment`; without it, nothing is posted.

Does the Malloy review modify my model files?▼

No. The skill never edits `.malloy` files; its only output is a Markdown review document. It also never posts PR comments unless `--comment` is explicitly passed, and it never walks above the resolved review scope.

What happens if Malloy MCP tools are unavailable during review?▼

The review degrades gracefully. Without `execute_query`, primary-key verification is marked skipped and the coverage gap is noted in the Scope section; without `search_malloy_docs`, capability checks are limited. The rubric-based LLM pass still runs.