diffs

Generate visual and file-based representations of text differences.

5.1k|1.2k|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/linuxhsj/openclaw-zero-token --skill diffs-linuxhsj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diffs
Source: https://github.com/linuxhsj/openclaw-zero-token/tree/main/extensions/diffs/skills/diffs
Command: npx skills add https://github.com/linuxhsj/openclaw-zero-token --skill diffs-linuxhsj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a standardized and shareable way to represent code or text changes, moving beyond manual edit summaries.

Core Features & Use Cases

  • Visual Diffs: Create interactive, gateway-hosted diff viewers for easy review.
  • File Artifacts: Generate image (PNG) or PDF artifacts of the diff for documentation or sharing.
  • Unified Patch Support: Accepts both before/after text and standard patch strings.
  • Use Case: When submitting a pull request, use this Skill to generate a visual diff that clearly highlights all changes made to a file, making the review process more efficient.

Quick Start

Use the diffs tool to create a viewer URL for the changes between the original text and the new text.

Frequently Asked Questions about diffs

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

FAQPage Schema
How do I generate a visual diff for code review?

To generate a visual diff, provide the before and after content or a unified patch string, and the tool outputs a gateway-hosted interactive viewer URL for clear code review communication.

Can I create a downloadable PDF or PNG file of a unified patch?

Yes, you can create downloadable PDF or PNG file artifacts from a unified patch string or provided text content for sharing and documentation purposes.

Does the visual diff tool support standard unified patch strings?

Yes, the visual diff tool supports standard unified patch strings as input, generating both interactive viewer URLs and file-based representations of text differences.

What is the best way to share code modifications for documentation?

The best way to share code modifications is to generate image or PDF artifacts of the text differences, providing a standardized visual representation for review and documentation.

What formats can I export text differences to?

You can export text differences to an interactive viewer URL, or generate downloadable file artifacts in PNG or PDF formats for clear communication of modifications.