diffs

Generate shareable diffs from text or patch inputs with viewer and file modes.

Updated Dec 6, 2016
One-click install
npx skills add https://github.com/majunbao/learn --skill diffs-majunbao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diffs
Source: https://github.com/majunbao/learn/tree/main/openclaw_tags/openclaw-2026.4.24/extensions/diffs/skills/diffs
Command: npx skills add https://github.com/majunbao/learn --skill diffs-majunbao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use the diffs tool to produce real, shareable diffs (viewer URL, file artifact, or both) instead of manual edit summaries.

Core Features & Use Cases

  • Accepts either before + after text, or a unified patch string.
  • Use mode=view for an interactive gateway-hosted viewer; mode=file to render artifacts; or mode=both to get both.
  • For large or high-fidelity outputs, use fileQuality (standard|hq|print) and optionally override fileScale and fileMaxWidth.
  • When delivering results, call the message tool and pass details.filePath.

Quick Start

Provide before and after text or a patch to generate a shareable diff and receive either a viewer URL or a file artifact.

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 text diff for code review?

To generate a shareable text diff for code review, provide before and after text or a unified patch string. The tool identifies differences between the two versions and renders them as an interactive viewer URL, a file artifact, or both.

Can I create a diff viewer from a unified patch string?

Yes, you can create a diff viewer from a unified patch string by using the mode=view option. This produces an interactive, gateway-hosted viewer that renders the patch input for documentation and review workflows.

What is the best way to document text differences for version control?

The best way to document text differences for version control is using mode=file or mode=both to render artifacts. You can adjust fileQuality settings to standard, hq, or print to tailor the output fidelity for your documentation needs.

Does this diff tool support high-quality file output for print documentation?

Yes, this diff tool supports high-quality file output for print documentation by setting fileQuality to print. You can also optionally override fileScale and fileMaxWidth to control the dimensions of the rendered artifact.

What input formats are supported for generating a text diff?

The supported input formats for generating a text diff are before and after text strings or a single unified patch string. These inputs are processed to identify differences and output a shareable viewer or file artifact.