菜单
Use when you need to generate tracked changes in Word documents from diff output, apply redlines from AI agents to DOCX files, or convert text diffs into native Word revisions.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ThomasMoreAI/legal-skills-open --skill redlines命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | redlines |
| title | redlines — Word Document Redlining Library |
| description | Use when you need to generate tracked changes in Word documents from diff output, apply redlines from AI agents to DOCX files, or convert text diffs into native Word revisions. |
| author | LegalQuants |
| author_url | https://github.com/LegalQuants/lq-skills/tree/main/skills/redlines |
| license | Apache-2.0 |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction |
| general |
| practice | general |
| language | en |
| tags | ["word","docx","tracked-changes","redlines","document-processing"] |
Takes diff output (from any source) and applies it to a DOCX as native Word tracked changes. Built by a practising Singapore counsel who needed deterministic document transformation.
DOCX with Word native tracked changes (insertions in blue, deletions in strikethrough)
import { applyRedlines } from '@houfu/redlines';
const result = applyRedlines({
originalDoc: './contract.docx',
modifiedText: 'modified contract text here',
author: 'LQClaw'
});
result.toDocx('./contract-redlined.docx');
Audience: legal engineers and counsel comfortable invoking a JavaScript library from a workflow. Not a self-service tool for a reviewing partner and not intended for non-technical users. The judgment as to which edits to apply sits upstream of this skill; this skill only carries them into the DOCX.
Work shape: Bounded Transactional primitive. Text-in (or diff-in) → DOCX-out. The transform is mechanical. It is not a redline reviewer, not a redline generator, and not a substantive review step.
This skill provides legal support, not legal advice. Producing a tracked-changes DOCX is mechanical document processing; the redlined output is a draft, not a vetted lawyer redline and not signed-off work product. A successful run means "the supplied edits were carried into the file as Word revisions" — not "these edits are correct" and not "this draft is fit to send."
Privilege and metadata exposure. Tracked changes carry author metadata into the document. The author field in the call (e.g., 'LQClaw') is written into the Word XML alongside revision timestamps and is preserved in the saved file. Anyone who opens the DOCX (counterparty, opposing counsel, recipient on production) can read it. Stance: AI authorship should be visible — do not mask AI-generated revisions behind a lawyer's name or firm identity. Treat the redlined DOCX as a draft document and assess data flow with the firm before routing draft files externally; redlines on privileged drafts can be discoverable and can affect privilege if circulated. Confirm a metadata-scrubbing step before any external delivery and confirm with the firm that the upstream diff and the source DOCX may be processed by the calling pipeline.
Accountability. Output is a mechanical transform of an upstream diff. A qualified, named lawyer must read the redlined DOCX page-by-page before any client or counterparty delivery. The skill does not stamp provenance, does not maintain an audit log, and does not designate an owner of the output — the calling workflow must do all three.
Stop and route to the responsible lawyer when:
Original author: Hou Fu Ang. Technical content (When to Use, How It Works, Input, Output, Usage, Key Design Decisions, Limitations) preserved verbatim.
LegalQuants applied QA remediation against the Legal Skill Design Framework on 2026-05-11 in response to the QA report at /tmp/qa-results/redlines.md (verdict: MATERIAL CONCERNS — three legal failure modes unaddressed). Added: version, last_reviewed, last_reviewed_by in frontmatter; Audience and Work Shape; Scope and Legal Use covering the three mandatory legal failure modes (advice-vs-support, privilege/metadata, accountability), with specific treatment of Word XML author metadata persistence and the stance that AI authorship should be visible rather than masked; Confidence Bands tied to document shape; Out of Scope ("does NOT do"); Escalation triggers. No changes to the technical instructions or the @houfu/redlines API.