skills/casedev/redline/SKILL.md
Compares two document versions and produces AI-powered redline analysis with structured change summaries, risk flags, and clause-by-clause breakdowns. Use when the user mentions "redline", "compare documents", "what changed", "version comparison", "contract diff", "track changes", or needs to understand differences between document versions.
npx skillsauth add casemark/skills redlineInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
AI-powered document comparison that goes beyond visual diffs. Upload two versions of a contract or legal document, get a structured analysis of what changed, what it means, and what to watch out for.
Requires the casedev CLI. See setup skill for installation and auth.
# Compare two local files
casedev redline compare ./contract-v1.pdf ./contract-v2.docx --json
# Compare two vault objects
casedev redline compare \
--vault VAULT_ID \
--base OBJECT_ID_V1 \
--target OBJECT_ID_V2 \
--json
casedev redline compare ./old-version.pdf ./new-version.docx --json
Accepts PDF, DOCX, DOC, and TXT. Mixed formats supported (e.g., PDF vs DOCX).
casedev redline compare \
--vault VAULT_ID \
--base OBJECT_ID \
--target OBJECT_ID \
--json
casedev redline compare \
--base-url "https://example.com/v1.pdf" \
--target-url "https://example.com/v2.pdf" \
--json
The default JSON output contains:
{
"summary": "Plain-English narrative of key changes",
"riskFlags": [
{
"severity": "high",
"clause": "Indemnification (Section 8.2)",
"change": "Cap reduced from $5M to $1M",
"impact": "Significantly increases exposure for indemnifying party"
}
],
"changes": [
{
"section": "Section 3.1 — Payment Terms",
"type": "modified",
"before": "Net 30 from invoice date",
"after": "Net 60 from invoice date",
"significance": "medium"
}
],
"stats": {
"sectionsModified": 12,
"sectionsAdded": 2,
"sectionsRemoved": 1,
"riskFlagsHigh": 1,
"riskFlagsMedium": 3
}
}
| Flag | Description |
|------|-------------|
| --format | Output format: json (default), markdown, text |
| --detail | Detail level: summary, standard (default), detailed |
| --focus | Comma-separated clause types to prioritize (e.g., indemnification,termination,liability) |
| --perspective | Analysis perspective: neutral (default), drafter, reviewer |
| --json | Shorthand for --format json |
summary — Executive overview only. Key changes and high-severity risk flags. Fast.standard — Full clause-by-clause breakdown with all risk flags. Default.detailed — Everything in standard plus original/modified text excerpts, suggested responses, and negotiation context.neutral — Objective analysis of changes.drafter — Flags changes that weaken your position (you drafted the original).reviewer — Flags changes you should push back on (you're reviewing incoming edits).A partner sends back a marked-up contract. See what changed and whether to worry:
casedev redline compare ./our-draft.docx ./their-markup.docx \
--perspective reviewer \
--detail summary \
--json
Focus analysis on the clauses that matter most:
casedev redline compare ./v3.pdf ./v4.pdf \
--focus "indemnification,limitation-of-liability,termination,governing-law" \
--detail detailed \
--json
Compare two versions already stored in a vault:
casedev redline compare \
--vault VAULT_ID \
--base OBJECT_ID_V1 \
--target OBJECT_ID_V2 \
--format markdown
Compare across multiple rounds to see the negotiation arc:
# Compare each consecutive pair
casedev redline compare --vault VAULT_ID --base V1_ID --target V2_ID --json > round1.json
casedev redline compare --vault VAULT_ID --base V2_ID --target V3_ID --json > round2.json
casedev redline compare --vault VAULT_ID --base V3_ID --target V4_ID --json > round3.json
| Format | Input | Notes | |--------|-------|-------| | PDF | ✅ | OCR applied automatically for scanned documents | | DOCX | ✅ | Preserves section/heading structure | | DOC | ✅ | Converted to DOCX internally | | TXT | ✅ | Plain text comparison |
Cross-format comparison is supported (e.g., compare a PDF against a DOCX).
"Unable to extract text": Document may be a scanned image without OCR text layer. Re-upload to a vault (automatic OCR) or use casedev ocr process first.
Large documents timeout: Documents over 200 pages may need --detail summary for faster processing.
"No significant changes found": Documents may be identical or near-identical. Check you're comparing the right versions.
Risk flags seem off: Use --perspective to align analysis with your role in the negotiation. Default neutral perspective doesn't assume a side.
development
name: automated-contract-summary language: en description: Generates structured executive summaries of contracts using ML — captures key terms, party obligations, risk allocations, and compliance requirements in a standardized format. Optimized for high-volume review where speed and consistency matter. tags: - summarization - agreement - corporate --- # Automated Contract Summarization Produces standardized executive summaries of contracts using machine learning, capturing essential term
tools
Extracts regulatory obligations from dense regulations across jurisdictions. Breaks down multi-level regulations into clear article-level obligations, classifies applicability to a business, and prioritizes by risk level. Use when translating regulations into actionable compliance requirements.
development
Continuously monitors regulatory landscapes for changes relevant to a specific business. Ingests global regulatory updates, filters by relevance, summarizes impact, and produces an actionable change advisory. Use when tracking regulatory developments affecting a particular product or market.
testing
Compares an organization's existing compliance controls, policies, and procedures against extracted regulatory obligations to identify coverage gaps. Produces a remediation plan with prioritized actions. Use when assessing compliance maturity or preparing for regulatory audits.