DOCX Reviewer
Enables Python-based tracking of revisions and audit trails in Microsoft Word documents.
Install
mkdir -p .claude/skills/docx-reviewer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13727" && unzip -o skill.zip -d .claude/skills/docx-reviewer && rm skill.zipInstalls to .claude/skills/docx-reviewer
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Skill for programmatically enabling track changes (Review Mode) and inserting revisions in Microsoft Word DOCX files using Python.Key capabilities
- →Enable or disable 'Track Changes' globally in a DOCX file
- →Insert programmatic `<w:ins>` tags for text insertions
- →Insert programmatic `<w:del>` tags for text deletions
- →Inject author metadata into revision tags
- →Inject timestamp metadata into revision tags
How it works
The skill modifies the `word/settings.xml` file within a DOCX document to enable track changes globally. For specific revisions, it manipulates the `WordprocessingML` structure by inserting `<w:ins>` and `<w:del>` XML elements.
Inputs & outputs
When to use DOCX Reviewer
- →Enable track changes programmatically
- →Insert revision metadata
- →Audit document edits
- →Automate document review
About this skill
📝 DOCX Reviewer (REVISION-01)
"What is changed must be seen. What is seen must be traceable." — Nachvollziehbarkeit
Purpose
The docx_reviewer skill enables the programmatic management of "Track Changes" (Review Mode) in Microsoft Word .docx documents. Since standard libraries like python-docx do not support this natively, this skill uses a combination of python-docx and deep XML manipulation of the WordprocessingML structure.
Capabilities
- Global Toggle: Enable or disable "Track Changes" for the entire document (any subsequent manual edits in Word will be tracked).
- Revision Injection (Advanced): Programmatically insert
<w:ins>(insertion) and<w:del>(deletion) tags to simulate a human reviewer's edits. - Audit Trail: Metadata injection for "Author" and "Timestamp" of revisions.
Prerequisites
- Python 3.x
python-docxlibrary (pip install python-docx)lxmllibrary (pip install lxml)
Implementation: Global Toggle (Track Changes)
To enable "Track Changes" in a document, the <w:trackRevisions /> element must be present in word/settings.xml.
Shared Command Line (Python)
import os
from docx import Document
from docx.oxml.shared import qn
from docx.oxml import OxmlElement
def enable_track_changes(doc_path, output_path=None):
"""
Enables 'Track Changes' in a DOCX file.
Note: This sets the global flag in settings.xml.
"""
doc = Document(doc_path)
# Access the settings XML
settings_root = doc.settings.element
# Find or create <w:trackRevisions />
track_revisions = settings_root.find(qn('w:trackRevisions'))
if track_revisions is None:
track_revisions = OxmlElement('w:trackRevisions')
settings_root.append(track_revisions)
if output_path:
doc.save(output_path)
else:
doc.save(doc_path)
return True
Implementation: Redlining (Tracked Edits)
To record a programmatic edit as a "Tracked Change" (redline), you cannot simply replace text. You must wrap the new text in a <w:ins> element and the removed text in a <w:del> element.
XML Structure for Insertion
<w:ins w:id="0" w:author="Antigravity" w:date="2026-03-26T14:45:00Z">
<w:r>
<w:t>New text content</w:t>
</w:r>
</w:ins>
Guidance for the Agent
- Enable Review Mode first by modifying
settings.xml. - Compare versions using
Python-Redlinesor by iterating through paragraphs and swappingw:tforw:ins/w:delblocks. - Always set the Author to
Antigravityor requested Persona for traceability.
Usage Scenarios
- LOI/Contract Review: Proposing changes while keeping the original visible.
- Patent Editing: Tracking claim updates for examiner review.
- Collaboration: Working with a USER who needs to see exactly WHAT was changed.
References
- ECMA-376 (Open XML Standard)
python-docxdocumentation- FEAT-307: LOI FANCCI Refinement workflow
When not to use it
- →When working with document formats other than DOCX
- →When standard `python-docx` functionality is sufficient for text manipulation
- →When needing to track changes manually within Microsoft Word
Prerequisites
Limitations
- →The skill is specific to Microsoft Word DOCX files.
- →It requires direct XML manipulation for advanced revision injection.
- →The skill does not natively support comparing document versions; it requires external tools or custom logic for that.
How it compares
This skill programmatically injects revision tags and metadata directly into the DOCX XML, which differs from manual review in Microsoft Word or standard `python-docx` operations that do not support revision tracking.
Compared to similar skills
DOCX Reviewer side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| DOCX Reviewer (this skill) | 0 | 2mo | Review | Advanced |
| docstring | 8 | 9mo | No flags | Beginner |
| pr-draft-summary | 3 | 4mo | No flags | Beginner |
| releasenote | 1 | 29d | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Hagenbefragen
View all by Hagenbefragen →You might also like
docstring
pytorch
Write docstrings for PyTorch functions and methods following PyTorch conventions. Use when writing or updating docstrings in PyTorch code.
pr-draft-summary
openai
Create a PR title and draft description after substantive code changes are finished. Trigger when wrapping up a moderate-or-larger change (runtime code, tests, build config, docs with behavior impact) and you need the PR-ready summary block with change summary plus PR draft text.
releasenote
DataDog
Create or update release notes for changes in the current branch using Reno, following dd-trace-py's conventions and the guidelines in docs/releasenotes.rst.
report-research
numerai
Write a complete Numerai experiment report in experiment.md (abstract, methods, results tables, decisions, next steps) and generate/link the standard show_experiment plot(s). Use after running any Numerai research experiments, or when a user asks for a “full report”, “write up”, “experiment.md update”, or “generate the standard plot”.
doc
ansys
Write, review, or edit PyMechanical documentation. Use when writing reStructuredText (RST) files, Python docstrings, Sphinx configurations, example scripts, README files, or any doc content for the PyMechanical library. This covers NumPy docstrings, RST file formatting, Google developer style guide
api-documenter
ovachiever
Auto-generate API documentation from code and comments. Use when API endpoints change, or user mentions API docs. Creates OpenAPI/Swagger specs from code. Triggers on API file changes, documentation requests, endpoint additions.