diffs

Generate shareable diffs from before/after text or unified patches.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/JOHNNYWHITEMIKE/openclaw --skill diffs-johnnywhitemike
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diffs
Source: https://github.com/JOHNNYWHITEMIKE/openclaw/tree/main/openclaw/.openclaw/openclaw/extensions/diffs/skills/diffs
Command: npx skills add https://github.com/JOHNNYWHITEMIKE/openclaw --skill diffs-johnnywhitemike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates unclear, non-verifiable edit summaries by generating real diffs you can share and review.

Core Features & Use Cases

  • Real, shareable diffs: Produces a viewer URL, a rendered file artifact, or both for the same before/after changes.
  • Flexible input formats: Accepts either before+after text or a unified patch string.
  • Practical review workflows: Use it to communicate changes in pull-request-like reviews, audits, or any situation where stakeholders need to see exact modifications.

Quick Start

Use the diffs tool to generate a viewer URL and a rendered artifact for the changes between the before text and the after text of your target file.

Frequently Asked Questions about diffs

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

FAQPage Schema
How do I generate a shareable diff from before and after text edits?▼

To generate a shareable diff, provide the before and after text of your file to the diffs tool, which produces a viewer URL and a rendered file artifact for inspecting exact modifications.

Can I use a unified patch string to create a visual code review output?▼

Yes, you can use a unified patch string to create a visual code review output, as the tool accepts either before+after text or a unified patch string to generate inspectable diffs.

What is the best way to replace vague manual edit summaries with verifiable change visualization?▼

The best way to replace vague manual edit summaries with verifiable change visualization is to generate real diffs, which output a viewer URL or file path showing exact before and after modifications.

Does the diffs tool support both viewer and file-render modes for artifact rendering?▼

Yes, the diffs tool supports both viewer and file-render modes with configurable output quality, returning a details.viewerUrl or details.filePath for downstream presentation of changes.

How do document comparison workflows handle before and after content transformation?▼

Document comparison workflows handle before and after content transformation by accepting both versions as input and generating an inspectable output, such as a viewer URL or rendered artifact, to communicate exact changes.