Metabase Documentation Review FAQs

Question 1

How does the feedback format help developers?

Accepted Answer

All feedback is strictly numbered (e.g., Issue 1, Issue 2), allowing developers to easily reference, discuss, and track the resolution of specific editorial points.

Question 2

What is the Metabase Documentation Review skill?

Accepted Answer

It is a specialized capability for Claude Code designed to review markdown files, ensuring they adhere to the specific writing standards and formatting rules of the Metabase style guide.

Question 3

What kind of style issues can it detect?

Accepted Answer

The skill checks for corporate jargon, improper UI element formatting (e.g., using backticks instead of bold), vague headings, 'easy' or 'simple' qualifiers, and broken link patterns.

Question 4

Can I use this for non-Metabase projects?

Accepted Answer

While specifically tuned for the Metabase style guide, its checks for readability, structure, and formatting provide a high standard of quality for any technical documentation project.

Question 5

Does this skill work with GitHub Pull Requests?

Accepted Answer

Yes, it features a dedicated PR review mode that uses GitHub MCP tools to create pending reviews and post sequential comments directly onto the pull request diff.

Metabase Documentation Review

Key Features

Use Cases

Metabase Documentation Review

Key Features

Use Cases