diffs

Generate shareable diffs from before/after text or patches.

121|17|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Zavianx/velaclaw --skill diffs-zavianx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diffs
Source: https://github.com/Zavianx/velaclaw/tree/main/extensions/diffs/skills/diffs
Command: npx skills add https://github.com/Zavianx/velaclaw --skill diffs-zavianx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produce real, shareable diffs for code changes using before/after text or a patch string, instead of relying on manual edit summaries.

Core Features & Use Cases

  • Generate diffs from before/after text or a patch input to create a downloadable patch or a viewer link.
  • Use in code reviews, documentation updates, and collaboration workflows where diff provenance is important.
  • Example: share a link to a live diff viewer or attach a patch to a pull request for precise change tracking.

Quick Start

Provide before and after text or a patch to generate a shareable diff 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 diff from before and after code text?

You can generate a shareable diff by providing before and after text inputs. The tool processes these text inputs to produce a downloadable patch file or a live viewer link for precise change tracking.

What is a patch string and how does it work for code reviews?

A patch string is a formatted text representation of code differences used for code reviews. Applying a patch string generates a real diff artifact, returning a viewer URL or file to track documentation updates and code changes.

Can I use a patch input to create a downloadable patch file?

Yes, you can use a patch input to create a downloadable patch file. By configuring the generation mode to handle patches, the tool processes the input and returns file artifacts suitable for attaching to pull requests.

Does the diff viewer support returning both a viewer URL and a file artifact?

Yes, the diff viewer supports returning both a viewer URL and a file artifact. Using mode=both returns a live shareable link alongside a downloadable patch file to support collaboration workflows needing diff provenance.

What's the best way to share code changes for collaboration workflows?

The best way to share code changes for collaboration workflows is to generate a real diff from before/after text or a patch. This produces a shareable viewer link or file artifact, ensuring clear diff provenance instead of manual edit summaries.

When do I need to use mode=view versus mode=file for version control diffs?

Use mode=view to return a live viewer URL for sharing a live diff, and mode=file to return a downloadable patch artifact. Use mode=both when collaboration workflows require both a viewer link and a file for version control.