Docs Review

This is built for reviewing Metabase documentation PRs against their house style guide. It catches the usual suspects: corporate speak like "utilize" instead of "use", burying the lede, linking the word "here", calling things "simple" or "easy". The smart bit is it can work two ways. If you're reviewing a GitHub PR, it posts all feedback as numbered inline comments in a single cohesive review. If you're working locally, it just lists everything in the conversation. Either way, every issue gets a number so you can say "fix 1, 3, and 5" without confusion. It's opinionated about what matters to readers and skips nitpicks that won't move the needle.

skills.sh installs: 2K
GitHub stars: 50.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add metabase/metabase --skill docs-review --agent claude-code

Installs into .claude/skills of the current project.

Files

Documentation Review Skill

@./../_shared/metabase-style-guide.md

Review mode detection

IMPORTANT: Before starting the review, determine which mode to use:

PR review mode: If the mcp__github__create_pending_pull_request_review tool is available, you are reviewing a GitHub PR
- Use the pending review workflow to post all issues as one cohesive review
- Follow the workflow steps in "PR review mode format" below
Local review mode: If the MCP tool is NOT available, output issues in the conversation
- Format all issues in a numbered markdown list (as described in "Feedback format" below)

Review process

Detect review mode - Check if mcp__github__create_pending_pull_request_review is available
Read the changes through once to understand intent
Check all issues that violate style guide or significantly impact readability
Only flag issues worth mentioning - if it won't make a material difference to the reader, skip it
REQUIRED: Number ALL feedback sequentially - Start from Issue 1 and increment for each issue found