docx-tracked-changes
Produce properly-formatted tracked changes for a Word document. Use when asked to redline a document, suggest edits to a contract or document, create tracked changes for review, or mark up a document with proposed revisions. Produces a complete redline with insertions, deletions, and margin comments that can be applied to the source document. Best used with Claude Opus 4.7 or newer for reliable tracked changes handling.
npx skills add mohitagw15856/pm-claude-skills --skill docx-tracked-changes --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Word Doc Tracked Changes Skill Produces properly-structured tracked changes for a Word document — insertions, deletions, replacements, and margin comments formatted so they can be applied directly to the source document. Built to leverage Opus 4.7 improvements in .docx redlining and tracked changes generation. ## Required Inputs Ask the user for these if not provided: - **The document** (paste the text or upload the .docx) - **Review type** (legal review / copy edit / substantive rewrite / compliance check / plain English rewrite) - **Review scope** (full document / specific sections / specific clause type) - **Reviewer role** (author / manager / legal counsel / subject matter expert) ## Output Structure ### 1. Redline Summary **Document:** [Name or identifier] **Review type:** [As stated] **Reviewer:** [Role] **Total changes:** [Insertions: N / Deletions: N / Comments: N] **Overall assessment:** [1-2 sentences — is this document close to final, or does it need substantial revision?] ### 2. Top-Level Changes Changes that affect the meaning or structure of the document: **Change N — [Section or paragraph reference]** - Original: "[Exact original text]" - Suggested: "[Proposed new
- Required Inputs
- Output Structure
- 1. Redline Summary
- 2. Top-Level Changes
- 3. Line-by-Line Tracked Changes
- 4. Margin Comments
- 5. Stylistic Edits
- 6. Pattern Flags
- 7. Review Completeness
- 8. How to Apply These Changes
- Quality Checks
- Anti-Patterns
- Example Trigger Phrases
- Why This Works Better on Opus 4.7
What does the docx-tracked-changes skill do?
Produce properly-formatted tracked changes for a Word document. Use when asked to redline a document, suggest edits to a contract or document, create tracked changes for review, or mark up a document with proposed revisions. Produces a complete redline with insertions, deletions, and margin comments that can be applied to the source document. Best used with Claude Opus 4.7 or newer for reliable tracked changes handling.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill docx-tracked-changes --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.