redlines

Convert diff output into DOCX files with native Word tracked changes.

46|25|Updated May 7, 2026
One-click install
npx skills add https://github.com/LegalQuants/lq-skills --skill redlines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redlines
Source: https://github.com/LegalQuants/lq-skills/tree/main/skills/redlines
Command: npx skills add https://github.com/LegalQuants/lq-skills --skill redlines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Producing a Word document with accurate tracked changes from AI edits is time-consuming and often results in non-native or unusable revision markup, especially when you start from diff output rather than manually editing in Word.

Core Features & Use Cases

  • Convert diff output into native DOCX revisions: Turn modified text or diff output into Word-compatible tracked changes (insertions and deletions) inside a DOCX.
  • Apply upstream edits deterministically: Use the mechanical transform to carry the supplied edits into the file as Word revisions without doing substantive redline review.
  • Preserve document structure: Keep headers, lists, and tables intact during the transformation so the output renders correctly in Microsoft Word.

Quick Start

Use the redlines skill to apply an AI-generated diff to an existing contract.docx and output a contract-redlined.docx with Word native tracked changes.

Frequently Asked Questions about redlines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert diff output into Word tracked changes in a DOCX file?

To convert diff output into Word tracked changes, this Skill mechanically transforms modified text or diffs into a DOCX file containing native Microsoft Word revision markup for insertions and deletions, preserving document structure like headers and tables.

Can I automatically apply AI-generated edits to a contract and produce a redlined DOCX?

Yes, you can automatically apply AI-generated edits to a contract and produce a redlined DOCX by supplying the diff output to this Skill, which deterministically writes the modifications as native Word tracked changes without requiring manual redline review.

Does converting diffs to Word revisions preserve document structure like tables and lists?

Converting diffs to Word revisions preserves document structure like tables and lists by applying a deterministic, format-preserving transformation that keeps headers, lists, and tables intact so the output renders correctly in Microsoft Word.

What is the best way to generate native Word revision markup from upstream diffs for legal documents?

The best way to generate native Word revision markup from upstream diffs for legal documents is using a deterministic transform that writes author metadata as part of the Word revision XML, ensuring format-preserving insertion and deletion markup for downstream rendering.

Why do my AI text edits result in non-native revision markup in Word?

AI text edits often result in non-native revision markup in Word when starting from diff output rather than manual editing, because the transformation lacks deterministic, format-preserving logic to write the edits as native Word revision XML.

Do I need Microsoft Word installed to generate DOCX files with tracked changes from diffs?

You do not need Microsoft Word installed to generate DOCX files with tracked changes from diffs, as this Skill directly writes the insertion and deletion markup into the Word revision XML to produce a DOCX file that is renderable downstream.