How does PR mode differ from Local mode?

In PR mode, the skill uses GitHub MCP tools to post comments directly to a pull request. In Local mode, it outputs a numbered list of issues within your current conversation.

Will it flag every minor grammatical error?

No, the skill is designed to only flag issues that make a material difference to the reader, avoiding unnecessary noise during the review process.

Does this work with any documentation style guide?

This specific skill is optimized for the Metabase writing style guide, covering its unique requirements for tone, formatting, and terminology.

Does it require specific tools to run?

It requires the standard Claude Code environment with access to Read, Grep, Bash, and Glob tools, plus GitHub MCP tools for PR functionality.

Metabase Style Docs Reviewer

Name: Metabase Style Docs Reviewer
Author: Microck

byMicrock

•

Content Management

Reviews documentation changes for compliance with the Metabase writing style guide across PRs and local files.

About

This skill automates the process of auditing documentation markdown files against the Metabase style guide, ensuring consistent tone, voice, and formatting. It intelligently detects whether it's operating within a GitHub Pull Request or a local environment, providing structured, numbered feedback on issues ranging from UI element bolding to conversational tone adjustments. By filtering out non-material changes, it helps developers and technical writers maintain high-quality, readable documentation with minimal manual overhead.

Key Features

Parallelized GitHub review comment submission for efficient PR workflows
89 GitHub stars
Sequential numbering of issues for easy tracking and referencing
Dual-mode operation for both local file reviews and GitHub Pull Request integration
Comprehensive checklist covering tone, structure, formatting, and code examples
Automated style guide compliance checks for Metabase writing standards

Use Cases

Automating technical documentation reviews during the GitHub PR process
Local auditing of markdown files before committing changes to a repository
Ensuring consistent terminology and formatting across large open-source documentation sets

About

Key Features

Parallelized GitHub review comment submission for efficient PR workflows
89 GitHub stars
Sequential numbering of issues for easy tracking and referencing
Dual-mode operation for both local file reviews and GitHub Pull Request integration
Comprehensive checklist covering tone, structure, formatting, and code examples
Automated style guide compliance checks for Metabase writing standards

Use Cases

Automating technical documentation reviews during the GitHub PR process
Local auditing of markdown files before committing changes to a repository
Ensuring consistent terminology and formatting across large open-source documentation sets