redline-conventions

Applies house conventions for tracked-changes and redline edits to matter documents.

72|19|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/sure-scale/doc-haus --skill redline-conventions-sure-scale
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redline-conventions
Source: https://github.com/sure-scale/doc-haus/tree/main/dochaus/skill/redline-conventions
Command: npx skills add https://github.com/sure-scale/doc-haus --skill redline-conventions-sure-scale

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Editing legal documents with AI risks ambiguous anchors, untracked silent edits, wrong authorship attribution, and unapproved language slipping into client contracts. This Skill enforces house conventions so every proposed change to a matter document is precisely located, tracked, attributed, and reviewable. ## Core Features & Use Cases - Exact-Text Anchoring: Locates edit targets by verbatim text copied from verified sources, with rules for making anchors unique and recovering from not-found or multi-match results. - Tool Selection Rules: Chooses between tracked-changes (word/phrase swaps), redline (whole-clause rewrites), and word-integration (silent edits only on explicit lawyer request). - Authorship & Playbook Compliance: Requires an author name on every change and mandates byte-exact copying of playbook approved language, stopping to ask when placeholders cannot be resolved. - Use Case: A lawyer asks to apply the firm's approved liability-cap language to an engagement letter; the Skill anchors to the exact clause, proposes the approved text as a tracked redline under the firm's name, and reports the change as pending accept/reject review. ## Quick Start Apply the playbook's approved limitation-of-liability clause to the engagement letter as a tracked redline attributed to the firm.

Frequently Asked Questions about redline-conventions

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

FAQPage Schema
How do I redline a contract clause with tracked changes?

Use the redline tool for whole-clause rewrites by passing a citation excerpt or sentence to locate the paragraph, and tracked-changes for surgical word or phrase swaps using exact find and replace text. Every proposal is recorded as a pending redline the lawyer accepts or rejects.

When should I use redline vs tracked-changes for document edits?

Use tracked-changes for the smallest word or phrase swap that satisfies the instruction. Use redline when the instruction reworks an entire clause, including when applying a playbook's approved replacement text.

Why does my edit anchor fail to match the document text?

Anchors must be copied verbatim from a search-document citation or read-document output; paraphrased or normalized text will not be found. If the text is not found, re-read the passage and anchor to text the document actually contains.

How do I handle anchors that match multiple locations in a contract?

Short phrases recur throughout contracts and the tool anchors to the first occurrence, which may be wrong. Extend the anchor with surrounding words from the same sentence until it uniquely matches the intended passage, then let the new proposal supersede the old one.

Can I make silent untracked edits to a legal document?

Silent edits via word-integration replace are only allowed when the lawyer explicitly asks for a clean change with no tracked revision. Every other change must be tracked, explained, and left pending the lawyer's accept or reject review.

How should playbook approved language be applied to a contract?

Copy text from approved or approved-fallback fences byte-exact into the replacement, with no rewording or additions. Use a fallback only when its stated condition is met, and stop to ask if a bracketed placeholder cannot be resolved from the matter.