diffs

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

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/PotLock/foxfang --skill diffs-potlock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diffs
Source: https://github.com/PotLock/foxfang/tree/main/extensions/diffs/skills/diffs
Command: npx skills add https://github.com/PotLock/foxfang --skill diffs-potlock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diff-based collaboration: generate machine-readable diffs instead of hand-written edit summaries, saving time and reducing miscommunication.

Core Features & Use Cases

  • Automated Diff Rendering: Convert before/after text or patch strings into shareable diff views.
  • Viewer & Artifact Outputs: Provide a live viewer URL, a file artifact, or both for distribution.
  • Use Case: Streamline code reviews, patches, and documentation updates across repositories.

Quick Start

Run the diffs tool to generate a patch view for your latest change.

Frequently Asked Questions about diffs

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

FAQPage Schema
How do I generate shareable diffs for code reviews instead of writing edit summaries?

To generate shareable diffs for code reviews, you can use a diffs tool that converts before/after text or patch strings into machine-readable artifacts, replacing manual edit summaries entirely. This streamlines collaborative reviews across repositories.

What output formats can I get when rendering patch views for collaborative documentation?

Rendering patch views for collaborative documentation provides a live viewer URL, a downloadable file artifact, or both simultaneously. You can configure file rendering options including fileFormat, fileQuality, and fileScale to suit distribution needs.

Can I use automated diff rendering for patch reviews across multiple repositories?

Yes, automated diff rendering applies directly to patch reviews and documentation updates across multiple repositories. It processes patch strings into machine-readable views, ensuring consistent communication and reducing miscommunication during version control collaboration.

Do I need to install the diffs tool before rendering code review artifacts?

Yes, you must install the diffs tool before rendering code review artifacts. The tool requires mode and rendering configurations—such as view, file, or mode=both—to process patch strings and generate the desired viewer or file outputs.

Why use machine-readable diffs over manual edit summaries for version control?

Machine-readable diffs save time and reduce miscommunication compared to manual edit summaries by automatically generating accurate patch views. This ensures precise code review and documentation collaboration without the risk of human error in summarizing changes.

What rendering modes are available for generating diff views and file artifacts?

Available rendering modes for generating diff views and file artifacts include viewer-only, file-only, or mode=both. These options let you choose between a live viewer URL, a static file, or both outputs for flexible distribution.