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".
Make the minimal change that resolves the issue. Research has already identified what to change — this skill handles the edit, formatting, self-review, and commit.
git checkout -b fix/issue-<number>-<short-desc> main
Use a short kebab-case description derived from the issue title (3-5 words).
Always read each file before modifying it. Make the minimal change that fixes the issue. Do not improve surrounding content, add comments, or address adjacent problems.
Follow the writing guidelines in CLAUDE.md, STYLE.md, and COMPONENTS.md.
Every content page requires title, description, and keywords in its
front matter. If any are missing from a file you touch, add them.
Prettier runs automatically after each edit via the PostToolUse hook. Run lint manually after all edits are complete:
${CLAUDE_SKILL_DIR}/scripts/lint.sh <changed-files>
The lint script runs markdownlint and vale on only the files you pass it, so the output is scoped to your changes. Fix any errors it reports.
Re-read each changed file: right file, right lines, change is complete,
front matter is present. Run git diff and verify only intended changes
are present.
Stage only the changed files:
git add <files>
git diff --cached --name-only # verify — no package-lock.json or other noise
git commit -m "$(cat <<'EOF'