foryourhealth111-pixel/docs-review
bundled/skills/docs-review/SKILL.md
Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.
$ install --global
skillsauthnpx skillsauth add foryourhealth111-pixel/vco-skills-codex docs-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 28, 2026, 9:20 PM36.1s1 file scanned
SKILL.md
- name:
- docs-review
- description:
- Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.
- allowed-tools:
- Read, Grep, Bash, Glob
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_reviewtool 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_reviewis 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
Review checklist
Run through the diff looking for these issues:
Tone and voice:
- [ ] Formal/corporate language ("utilize" not "use", "offerings", etc.)
- [ ] "Users" instead of "people" or "companies"
- [ ] Excessive exclamation points or overly peppy tone
- [ ] Telling readers something is cool instead of showing them
Structure and clarity:
- [ ] Important information buried instead of leading
- [ ] Verbose text that adds little value
- [ ] Paragraphs without clear purpose
- [ ] Vague headings that don't convey the point
- [ ] Instructions explain "why" before telling "what to do"
- [ ] Tasks described as "easy" or "simple"
Links and references:
- [ ] Linking the word "here" instead of descriptive text
- [ ] Links in headings (unless entire heading is a link)
Formatting:
- [ ] Ampersands as "and" substitute (except proper nouns)
- [ ] Inconsistent list formatting
Code and examples:
- [ ] Code examples that don't work or would error
- [ ] Commands not in execution order
- [ ] Full-width screenshots instead of scoped UI elements
- [ ] Excessive or unnecessary images
Sentence construction:
- [ ] Overuse of pronouns when introducing new terms
Quick scan table
| Pattern | Issue | | ----------------------------- | --------------------------------------------- | | we can do X, our feature | Should be "Metabase" or "it" | | click here, read more here | Need descriptive link text | | easy, simple, just | Remove condescending qualifiers | | users | Should be "people" or "companies" if possible |
Feedback format
MANDATORY REQUIREMENT: Every single issue MUST be numbered sequentially starting from Issue 1.
This numbered format is NON-NEGOTIABLE. It allows users to efficiently reference specific issues (e.g., "fix issues 1, 3, and 5") and track which feedback has been addressed.
Local review mode format
When outputting issues in the conversation (local mode), use this format:
## Issues
**Issue 1: [Brief title]**
Line X: Succinct description of the issue
[code or example]
Suggested fix or succinct explanation
**Issue 2: [Brief title]**
Line Y: Description of the issue
Suggested fix or explanation
**Issue 3: [Brief title]**
...
Examples:
Issue 1: Formal tone Line 15: This could be more conversational. Consider: "You can't..." instead of "You cannot..."
Issue 2: Vague heading Line 8: The heading could be more specific. Try stating the point directly: "Run migrations before upgrading" vs "Upgrade process"
PR review mode format
When posting to GitHub (PR mode), use the pending review workflow:
Workflow steps:
-
Start a review: Use
mcp__github__create_pending_pull_request_reviewto begin a pending review- This creates a draft review that won't be visible until submitted
-
Get diff information: Use
mcp__github__get_pull_request_diffto understand the code changes and line numbers- This helps you determine the correct file paths and line numbers for comments
-
Identify ALL issues: Read through all changes and identify every issue worth mentioning
- Collect all issues before posting any comments
- Number them sequentially (Issue 1, Issue 2, Issue 3, etc.)
-
Add review comments: Use
mcp__github__add_pull_request_review_comment_to_pending_reviewfor each issue- CRITICAL: Post ALL comments in a SINGLE response using multiple tool calls in parallel
- Each comment should reference a specific file path and line number from the diff
- Start each comment body with
**Issue N: [Brief title]** - Include the description and suggested fix
-
Submit the review: Use
mcp__github__submit_pending_pull_request_reviewto publish all comments at once- Use event type
"COMMENT"(NOT "REQUEST_CHANGES") to make it non-blocking - Do NOT include a body message - Leave the body empty or omit it entirely
- All comments will appear together as one cohesive review
- Use event type
Comment format example:
**Issue 1: Formal tone**
This could be more conversational. Consider: "You can't..." instead of "You cannot..."
IMPORTANT:
- Each issue gets its own review comment attached to the pending review
- Number ALL comments sequentially (Issue 1, Issue 2, Issue 3, etc.)
- Always start the comment body with
**Issue N: [Brief title]** - MUST add all comments in parallel in a single response - Do NOT add them one after another in separate responses
- Do NOT output a summary message to the conversation - only post GitHub review comments
- When submitting the review, do NOT include a body parameter (or leave it empty) to avoid cluttering the PR with summary text
- The review will appear as a single review with multiple comments when submitted
Final check
- Remove any issues from your assessment that won't make a material difference to the reader if addressed. Only flag issues worth the author's time to fix.
- Verify all issues are numbered sequentially starting from Issue 1 with no gaps in numbering.
- Confirm the format exactly matches:
**Issue N: [Brief title]**where N is the issue number. - In PR mode: Verify each issue was posted as a separate GitHub comment (not output to conversation).
Related Skills
foryourhealth111-pixel/shap
development
VerifiedTrustedCommunity
Model interpretability and explainability using SHAP (SHapley Additive exPlanations). Use this skill when explaining machine learning model predictions, computing feature importance, generating SHAP plots (waterfall, beeswarm, bar, scatter, force, heatmap), debugging models, analyzing model bias or fairness, comparing models, or implementing explainable AI. Works with tree-based models (XGBoost, LightGBM, Random Forest), deep learning (TensorFlow, PyTorch), linear models, and any black-box model.
1,760SKILL.mdUpdated Apr 27, 2026
foryourhealth111-pixel/sentry
development
VerifiedTrustedCommunity
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
1,760SKILL.mdUpdated Apr 27, 2026
foryourhealth111-pixel/senior-prompt-engineer
development
VerifiedTrustedCommunity
World-class prompt engineering skill for LLM optimization, prompt patterns, structured outputs, and AI product development. Expertise in Claude, GPT-4, prompt design patterns, few-shot learning, chain-of-thought, and AI evaluation. Includes RAG optimization, agent design, and LLM system architecture. Use when building AI products, optimizing LLM performance, designing agentic systems, or implementing advanced prompting techniques.
1,760SKILL.mdUpdated Apr 27, 2026
foryourhealth111-pixel/senior-ml-engineer
development
VerifiedTrustedCommunity
World-class ML engineering skill for productionizing ML models, MLOps, and building scalable ML systems. Expertise in PyTorch, TensorFlow, model deployment, feature stores, model monitoring, and ML infrastructure. Includes LLM integration, fine-tuning, RAG systems, and agentic AI. Use when deploying ML models, building ML platforms, implementing MLOps, or integrating LLMs into production systems.
1,760SKILL.mdUpdated Apr 27, 2026