doc-pr
Orchestrate an editorial review for pull requests targeting dev. Reviews changed markdown files and posts a structured comment to the PR. Vale and Dale issues are auto-fixed separately by the vale-autofix workflow. Use this skill whenever a PR involves markdown files in docs/ and targets the dev branch — triggered automatically by the doc-pr GitHub Actions workflow on PR open, sync, or when invoked manually via /doc-pr.
87
88%
Does it follow best practices?
Impact
77%
1.92xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Evaluation results
32%
-4%Documentation PR Review
Editorial review output format and idiom tagging
Correct top-level heading
50%
0%
Editorial Review subheading
0%
0%
File path listed
50%
50%
Priority category labels used
50%
30%
Idiom tagged with [idiom]
0%
0%
Issues only on added lines
40%
100%
Suggested fix included
100%
62%
Summary section present
57%
42%
Summary mentions Vale/Dale
0%
0%
What-to-do-next footer present
0%
0%
@claude instructions listed
0%
0%
Uses computer vs workstation
100%
100%
100%
70%Documentation PR Review — Mixed File Types
KB file exclusion from editorial review
KB file excluded from review
0%
100%
Non-KB file reviewed
100%
100%
Correct top-level heading
0%
100%
Editorial Review subheading
0%
100%
Priority category labels used
0%
100%
Added-lines-only scope
90%
100%
Idiom identified
0%
100%
Summary section present
57%
100%
Vale/Dale mention in summary
0%
100%
Mandatory footer present
0%
100%
Files not modified
100%
100%
100%
44%Documentation PR Review
All-KB-files no-review edge case
No KB editorial analysis
0%
100%
No-reviewable-files message
0%
100%
Review file written
100%
100%
Correct heading present
0%
100%
KB files not modified
100%
100%
No Vale or Dale execution
100%
100%
No idiom analysis on KB content
100%
100%
Reads CLAUDE.md before acting
100%
100%
Diff read from inputs path
100%
100%
- Repository
- netwrix/docs
- Commit
6b797b3
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.