docs-review — Claude Code skill: review docs against a style guide
This skill checks markdown documentation changes against the Metabase style guide and returns a numbered list of issues.
npx skills add metabase/metabase --skill docs-review -a claude-codeWhat docs-review does
The skill fires when a diff touches docs/**/*.md. It reads the changes once to understand intent, then walks a checklist: tone and voice, structure, links, formatting, code examples, sentence construction. Every issue gets a number starting at Issue 1, so an author can point at specific ones.
There are two modes. With the mcp__github__create_pending_pull_request_review tool available, the skill opens a pending review, collects all comments and publishes them as one review through mcp__github__submit_pending_pull_request_review using the COMMENT event type. Without that MCP tool, issues are printed into the conversation as a numbered list.
Under the hood it pulls in a shared style guide file, _shared/metabase-style-guide.md, plus a quick scan table: “click here” instead of descriptive link text, “easy” and “simple” as condescending qualifiers, “users” where “people” or “companies” fits. Allowed tools are Read, Grep, Bash and Glob. The pull request mode needs a GitHub MCP server connected — otherwise you only get local output.
What it helps with
- check markdown edits under
docs/before merging - catch condescending wording like “easy” and “simple”
- replace “click here” with descriptive link text
- spot code examples that would error
- post one review instead of scattered comments
Example prompts for the agent
- Review the documentation changes against the Metabase style guide
- Run docs-review on the
docs/diff and number the issues - Post the documentation issues as a pull request review
How to install docs-review
1Skills CLI (Vercel)
npx skills add metabase/metabase --skill docs-review -a claude-code2Manually: put the files in place
~/.claude/skills/docs-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/docs-review/
1Skills CLI (Vercel)
npx skills add metabase/metabase --skill docs-review -a codex2Manually: put the files in place
.agents/skills/docs-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add metabase/metabase --skill docs-review -a cursor2Manually: put the files in place
.cursor/skills/docs-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install metabase/metabase docs-review2Manually: put the files in place
.github/skills/docs-review/SKILL.md1Skills CLI (Vercel)
npx skills add metabase/metabase --skill docs-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/metabase/metabase --path .claude/skills/docs-reviewManually: put the files in place
.devin/skills/docs-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add metabase/metabase --skill docs-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about docs-review
How do I install docs-review in Claude Code?
Run npx skills add metabase/metabase --skill docs-review -a claude-code. The skill lands in ~/.claude/skills/docs-review/SKILL.md.
What does docs-review do?
It reviews markdown documentation changes against the Metabase style guide and returns a numbered list of issues with suggested fixes.
How do the two review modes differ?
With the mcp__github__create_pending_pull_request_review tool available, issues go to the pull request as comments in a single review. Without it, the skill prints them in the conversation.