render-diff

Transform git diff output into review-ready 4-column tables with file headers and hunk boxes.

101|2|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/cowwoc/cat --skill render-diff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: render-diff
Source: https://github.com/cowwoc/cat/tree/main/plugin/skills/render-diff
Command: npx skills add https://github.com/cowwoc/cat --skill render-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Transform raw git diff output into a review-ready 4-column table with fenced headers equivalent to a compact, readable presentation for code reviews and approvals.

Core Features & Use Cases

  • 4-column hunk boxes with repeated file headers for quick scanning
  • Word-level diff markers and context to highlight changes
  • Use Case: Ideal for approval gates, code reviews, and change summaries where diffs must be clearly understood at a glance.

Quick Start

Use the render-diff skill to process a diff stream or file and output a ready-to-review table.

Frequently Asked Questions about render-diff

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

FAQPage Schema
How do I format a git diff for a code review?

To format a git diff for code review, you can use a dedicated script to transform raw diff output into a review-ready 4-column table with fenced file headers and word-level change markers for quick scanning.

What is the best way to display code changes for approval gates?

Displaying code changes for approval gates is best handled by rendering raw diffs into compact 4-column hunk boxes with repeated file headers, allowing reviewers to clearly understand changes at a glance.

Can I pre-compute diff outputs for automated gating processes?

Yes, you can use the render-diff script to process and pre-compute diff streams or files into review-ready tables, supporting automated approval gates that require clearly formatted change summaries.

Does the 4-column diff format show word-level changes or just line-level?

The 4-column diff format shows both line-level and word-level changes. It includes word-level diff markers and context within the hunk boxes to highlight specific modifications for succinct reviewing.

How do I make large pull request diffs easier to scan?

Make large pull request diffs easier to scan by transforming raw output into a 4-column table with repeated file headers above each hunk box, ensuring quick visual identification of modified files and specific changes.