document-redliner

Automated document comparison, redline generation, change tracking

509 stars

Best use case

document-redliner is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Automated document comparison, redline generation, change tracking

Teams using document-redliner should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/document-redliner/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/library/specializations/domains/business/venture-capital/skills/document-redliner/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/document-redliner/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How document-redliner Compares

Feature / Agentdocument-redlinerStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Automated document comparison, redline generation, change tracking

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Document Redliner

## Overview

The Document Redliner skill provides automated document comparison and redline generation for deal negotiations. It enables efficient tracking of changes across document versions and supports the definitive document negotiation process.

## Capabilities

### Document Comparison
- Compare document versions automatically
- Identify additions, deletions, and modifications
- Track formatting and structural changes
- Handle multi-party document exchanges

### Redline Generation
- Generate visual redline documents
- Create summary of material changes
- Produce change statistics and metrics
- Support multiple output formats

### Change Tracking
- Maintain full document history
- Track changes by party/source
- Provide change audit trail
- Support rollback to previous versions

### Negotiation Support
- Highlight substantive vs. minor changes
- Flag changes requiring attention
- Track issue resolution status
- Generate negotiation status reports

## Usage

### Compare Documents
```
Input: Two document versions
Process: Analyze differences
Output: Comparison report, change list
```

### Generate Redline
```
Input: Original, modified documents
Process: Create marked-up version
Output: Redlined document, change summary
```

### Track Negotiation Progress
```
Input: Document exchange history
Process: Analyze negotiation state
Output: Progress report, open issues
```

### Summarize Changes
```
Input: Redlined document
Process: Extract and summarize changes
Output: Executive change summary
```

## Document Types Supported

| Document | Typical Sections Tracked |
|----------|-------------------------|
| Stock Purchase Agreement | Reps, warranties, conditions |
| Investor Rights Agreement | Rights, obligations, governance |
| Voting Agreement | Voting provisions, board composition |
| Right of First Refusal | Transfer restrictions, procedures |
| Certificate of Incorporation | Share rights, preferences |

## Integration Points

- **Definitive Document Negotiation**: Core redlining skill
- **Contract Extractor**: Extract terms from documents
- **Closing Checklist Tracker**: Track doc completion
- **Deal Counsel Coordinator (Agent)**: Support legal work

## Comparison Features

| Feature | Description |
|---------|-------------|
| Word-level diff | Character-by-character changes |
| Semantic comparison | Meaning-based analysis |
| Structure tracking | Section/paragraph changes |
| Cross-reference checking | Internal reference consistency |

## Best Practices

1. Establish clean base document for comparison
2. Use consistent document naming conventions
3. Review substantive changes carefully
4. Maintain organized version history
5. Summarize changes for non-legal stakeholders

Related Skills

clinical-documentation-query

509
from a5c-ai/babysitter

Generate compliant physician queries to clarify clinical documentation for accurate coding, severity of illness, and risk of mortality capture

collection-documentation

509
from a5c-ai/babysitter

Create and maintain comprehensive collection records including cataloging, photography, condition documentation, and database management following AAM/ICOM standards

latex-document-compiler

509
from a5c-ai/babysitter

Skill for compiling and managing LaTeX documents

latex-physics-documenter

509
from a5c-ai/babysitter

LaTeX scientific documentation skill specialized for physics papers with equation rendering and journal formatting

rfx-document-generator

509
from a5c-ai/babysitter

Automated RFI/RFP/RFQ document creation skill with template management and evaluation criteria

standard-work-documenter

509
from a5c-ai/babysitter

Standardized work procedure documentation skill with time observations, work sequence analysis, and visual work instructions

pip-documentation

509
from a5c-ai/babysitter

Create legally compliant performance improvement plan documentation with evidence tracking and milestone management

documentation-generator

509
from a5c-ai/babysitter

Generate documentation for migrated systems including API docs, architecture docs, and runbooks

decision-documentation

509
from a5c-ai/babysitter

Create Architecture Decision Records (ADRs) documenting significant technical choices with context, options, consequences, and sequential numbering.

Project Documentation

509
from a5c-ai/babysitter

Generate comprehensive project documentation with source tree analysis and Mermaid diagrams.

process-builder

509
from a5c-ai/babysitter

Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.

Workflow & Productivity

babysitter

509
from a5c-ai/babysitter

Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)