skills.rest
zyj18860969891-byte
zyj18860969891-byteCOMMUNITY
Explore all skills by this author →
GitHub

diffs

Generate shareable diffs and patch views with viewer URLs and file artifacts.

Updated Jan 31, 2026
Search Tags:#diff#patch#code-review#diffs#viewer
One-click install
npx skills add https://github.com/zyj18860969891-byte/openclaw-railway --skill diffs-zyj18860969891-byte
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diffs
Source: https://github.com/zyj18860969891-byte/openclaw-railway/tree/main/extensions/diffs/skills/diffs
Command: npx skills add https://github.com/zyj18860969891-byte/openclaw-railway --skill diffs-zyj18860969891-byte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables you to produce real, shareable diffs and patch views for code changes, replacing manual edit summaries with precise records of changes.

Core Features & Use Cases

  • Diff rendering: generate before/after diffs and patch data that can be viewed or embedded as artifacts.
  • Viewer & artifacts: provide a gateway-hosted viewer URL or render a file artifact for distribution.
  • Use Case: in a code review, compare a feature branch against main and share a link or artifact with stakeholders who do not have direct repo access.

Quick Start

Use the diffs tool to generate a viewer URL for the changes in the attached patch.

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 view for code review?▼

To generate a shareable diff view for code review, you use a dedicated diffs tool to render patch data into a viewer URL or file artifact. This allows stakeholders without direct repo access to view the real before/after changes instantly and securely.

Can I share code diffs with stakeholders who do not have repository access?▼

Yes, you can share code diffs with stakeholders lacking repository access by rendering a file artifact or providing a viewer URL. This allows external reviewers to see precise before/after patch views without needing direct codebase permissions.

What is the best way to track code changes across a feature branch?▼

The best way to track code changes across a feature branch is to generate real before/after diffs and patch data. This produces precise records of changes that can be embedded as artifacts or viewed via a dedicated viewer URL.

Does generating a patch view require a specific diffs tool?▼

Yes, generating a patch view requires a dedicated diffs tool to render viewer URLs and file artifacts. The tool supports a viewerBaseUrl and multiple modes to properly display the before/after code changes.

When do I need to render a file artifact instead of a viewer URL?▼

You need to render a file artifact instead of a viewer URL when distributing code changes offline or embedding patch views directly into external systems. Both methods provide precise before/after diffs for stakeholders without repo access.

Related Skills

Explore More Software Engineering Skills→
wuv-dreamguidewuv-dreamguide

diffs

Generate shareable diffs from code changes with optional viewer URLs.

Official
Intermediate
nuno7lopesnuno7lopes

diffs

Generate shareable file or viewer diffs from text and patch strings.

Community
Basic
dtsongdtsong
1

git-status

Executes Git commands via Bash for repository status, diffs, logs, and blame.

Community
Basic
franklinbaldofranklinbaldo
2

github-api

Transform GitHub URLs into plain-text diffs, patches, raw files, and feeds.

Community
Basic