diffs

Name: diffs
Availability: InStock
Author: StoryClaw

Generate visual and file-based code diffs from before/after text or patch strings.

Updated Feb 11, 2026

Search Tags:#developer tools #code review #collaboration #version control #diff

Ready to run

npx skills add https://github.com/storyclaw-official/storyclaw-assistant --skill diffs-storyclaw-official

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diffs
Source: https://github.com/storyclaw-official/storyclaw-assistant/tree/main/extensions/diffs/skills/diffs
Command: npx skills add https://github.com/storyclaw-official/storyclaw-assistant --skill diffs-storyclaw-official

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill replaces manual edit summaries with real, shareable diffs, making code changes clearer and more professional.

Core Features & Use Cases

Generate Diffs: Create visual diffs from before/after text or patch strings.
Multiple Output Modes: Choose between an interactive viewer URL, a file artifact (PNG/PDF), or both.
Use Case: When proposing a code change, instead of describing what you changed, use this Skill to generate a diff URL that others can view directly in their browser.

Quick Start

Use the diffs tool to generate 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 shareable code diff from before and after text?▼

To generate a code diff, provide the original and modified text or patch strings to produce a visual comparison. The output can be an interactive viewer URL or a downloadable PNG/PDF file artifact for collaboration.

Can I output my code differences as a PNG or PDF file?▼

Yes, code differences can be exported as a PNG or PDF file artifact. This allows you to share static visual representations of code modifications directly with reviewers or attach them to documentation.

What is the best way to visually communicate code modifications for review?▼

The best way to communicate code modifications is generating a visual diff using before and after text. This replaces manual edit summaries with an interactive viewer URL or downloadable file for precise review.

Does this diff generator support patch strings as input?▼

Yes, the diff generator supports patch strings as input alongside standard before and after text. It processes these patch strings to create visual code differences suitable for team collaboration.

How do I use an interactive viewer URL for code review collaboration?▼

You use an interactive viewer URL by generating a diff from your code changes and sharing the link. Reviewers can then open the gateway-hosted viewer directly in their browser to inspect the modifications.

When should I avoid using manual edit summaries for code changes?▼

You should avoid manual edit summaries when proposing complex code changes that require precise visual context. Generating a shareable diff ensures reviewers see exact modifications rather than relying on text descriptions.