write
Write a documentation fix on a branch. Makes the minimal change, formats, self-reviews, and commits. Use after research has identified what to change. "write the fix", "make the changes", "implement the fix for #1234".
93
92%
Does it follow best practices?
Impact
93%
2.26xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
90%
60%Fix Installation Instructions
Branch naming and commit format discipline
Branch prefix
0%
100%
Issue number in branch
0%
100%
Branch suffix length
0%
0%
Commit subject prefix
0%
100%
Fixes reference
0%
100%
Subject length
100%
100%
Problem sentence
100%
100%
Solution sentence
0%
100%
Co-Authored-By trailer
0%
100%
Minimal change
100%
100%
90%
30%Fix Misleading Default in Configuration Docs
Front matter enforcement on touched files
description added
0%
100%
keywords added
0%
100%
keywords is a list
0%
100%
title preserved
100%
100%
timeout default corrected
100%
100%
overview.md unmodified
100%
100%
No surrounding improvements
100%
0%
No inline comments added
100%
100%
Front matter position
100%
100%
Commit subject format
0%
100%
100%
65%Correct Terminology in API Documentation
Vendored-file exclusion and lint correction
Content fix applied
100%
100%
_vendor not modified
0%
100%
data/cli not modified
0%
100%
Heading blank lines fixed
0%
100%
Trailing spaces removed
0%
100%
guide.md unmodified
100%
100%
Minimal change scope
100%
100%
changes.md accuracy
0%
100%
Commit subject format
0%
100%
Commit body present
100%
100%
- Repository
- docker/docs
- Commit
c0aa985
- 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.