skills.rest
adamhjouj
adamhjoujCOMMUNITY
Explore all skills by this author →
Website𝕏@adamk_issaGitHub

diffs

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

4|1|Updated Mar 6, 2026
Search Tags:#documentation#patch#code-review#diffs#viewer#diff-rendering
One-click install
npx skills add https://github.com/adamhjouj/shieldclaw --skill diffs-adamhjouj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diffs
Source: https://github.com/adamhjouj/shieldclaw/tree/main/openclaw/extensions/diffs/skills/diffs
Command: npx skills add https://github.com/adamhjouj/shieldclaw --skill diffs-adamhjouj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diff-based collaboration is often manual and error-prone. This Skill enables generating real, shareable diffs to clearly communicate changes between before and after text, avoiding tedious edit summaries.

Core Features & Use Cases

  • Diff rendering from before/after text or patch strings with an option to provide a gateway-hosted viewer URL, a rendered artifact, or both.
  • Multiple modes: mode=view, mode=file, mode=both; optional file formats like PNG or PDF for rendered artifacts.
  • Use cases include code reviews, documentation edits, and patch submissions by producing precise, auditable diffs.

Quick Start

Provide the before and after texts and request a shareable diff with a viewer URL.

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 for before and after text?▼

You can generate a shareable diff by providing before and after text or patch strings, which returns a viewer URL, a rendered artifact, or both. This replaces manual edit summaries with precise change traces.

What is the best way to show code changes during a patch submission?▼

The best way to show code changes during patch submissions is to generate a real, shareable diff from before and after text. This provides a clear, auditable change trace that replaces tedious manual edit summaries.

Can I export a rendered diff as a PNG or PDF file?▼

Yes, you can export a rendered diff as a PNG or PDF file. By setting mode=file or mode=both, the output generates a rendered artifact in your specified file format alongside optional viewer URL guidance.

Does the diff viewer support patch string inputs for documentation edits?▼

Yes, the diff viewer supports patch string inputs for documentation edits. It processes patch strings to produce precise change traces, offering a gateway-hosted viewer URL or rendered artifact for clear communication.

What are the available output modes for diff rendering?▼

The available output modes for diff rendering are mode=view, mode=file, and mode=both. These modes determine whether you receive a gateway-hosted viewer URL, a rendered artifact like a PNG or PDF, or both outputs simultaneously.

Related Skills

Explore More Software Engineering Skills→
openclaw-easyopenclaw-easy
14

diffs

Render before/after text or patch strings as shareable diff artifacts.

Community
Intermediate
enclawedenclawed
2

diffs

Generate shareable diffs from text or unified patches with viewer URLs and PNG or PDF artifacts.

Community
Intermediate
qianleigoodqianleigood
30

diffs

Generate unified diffs from before/after text or patch inputs.

Community
Intermediate
JnusoJnuso

diffs

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

Community
Intermediate