Autonomous fixer for documentation content issues. Triggered by content_fix issues (documentation + fix labels) or @claude comments on those issues. Reads the issue, identifies affected files, applies fixes following Netwrix writing standards, and pushes a branch. A separate workflow step creates the PR. Asks clarifying questions if the request is ambiguous.
96
96%
Does it follow best practices?
Impact
96%
1.60xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
URL path mapping and required output format
URL to path mapping
33%
100%
Both path variants checked
25%
100%
Branch naming convention
100%
100%
Commit message prefix
0%
100%
Co-authored-by trailer
0%
100%
BRANCH_NAME output line
0%
100%
Files modified listed
62%
100%
Narrow fix only
100%
100%
No PR creation mentioned
0%
100%
docs/CLAUDE.md consulted
100%
100%
Vague and image-only issue stop conditions
Issue 17 stop decision
100%
100%
Issue 17 asks what to change
100%
100%
Issue 23 stop decision
100%
100%
Issue 23 cites team member
100%
100%
No branch created for either
100%
100%
No PR creation mentioned
100%
100%
Distinct stop reasons
100%
100%
Issue 17 comment is specific
100%
100%
No meaning changes attempted
100%
100%
docs/CLAUDE.md acknowledged
0%
0%
Product directory search and scoped fix workflow
Product directory mapping
60%
100%
Keyword grep used
100%
100%
docs/CLAUDE.md read step
100%
100%
Branch name format
0%
100%
Commit message format
0%
100%
Co-authored-by in commit
0%
100%
BRANCH_NAME output line
0%
100%
Files modified listed
100%
100%
Fix is scoped narrowly
100%
100%
No PR or issue comment step
0%
100%
No Vale/Dale run
100%
100%
6b797b3
Table of Contents
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.