diffs

Generate unified diffs from before/after text or patch strings.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/MaxSaiets/myOpenCL --skill diffs-maxsaiets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diffs
Source: https://github.com/MaxSaiets/myOpenCL/tree/main/openclaw/extensions/diffs/skills/diffs
Command: npx skills add https://github.com/MaxSaiets/myOpenCL --skill diffs-maxsaiets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams show exact changes between document revisions by producing real, shareable diffs instead of manual edit summaries.

Core Features & Use Cases

  • Generate unified diffs from before/after text or patch strings.
  • Provide a viewer URL or a rendered diff artifact for easy sharing and review.
  • Supports interactive viewing, batch processing, and integration with code review workflows.

Quick Start

Provide before and after text to generate a shareable diff.

Frequently Asked Questions about diffs

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

FAQPage Schema
How do I create a shareable diff from code changes?

You can generate a unified diff by providing before and after text or a patch string. The output is a viewer URL or rendered artifact that you can share for code reviews across multiple files and branches.

What is a unified diff and when do I need it for code reviews?

A unified diff is a standard text format showing exact line-by-line changes between file revisions. You need it for code reviews and patch reviews to display modifications across multiple files without writing manual edit summaries.

Can I generate a diff viewer URL from a patch string?

Yes, you can generate a diff viewer URL by inputting a patch string. The tool processes the patch file format and outputs a shareable viewer URL or rendered artifact for interactive viewing during code reviews.

Does this diff viewer support batch processing for multiple files?

Yes, the diff viewer supports batch processing for multiple files and branches. You can input before and after text combinations to generate rendered artifacts for comprehensive code reviews and documentation updates.

What is the best way to share code diffs for patch reviews?

The best way to share code diffs is to generate a viewer URL or rendered artifact. Inputting before and after text produces a shareable, interactive diff that integrates smoothly into existing code review workflows.

What are the limitations of using rendered artifacts for code diffs?

Rendered artifacts require input as before and after text or patch strings. A limitation is that without proper text or patch input, the tool cannot generate a viewer URL or accurately display the code diffs for review.