diff-story

Generate technical narratives from git commit history and diffs.

3|2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/joyehuang/skills --skill diff-story
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diff-story
Source: https://github.com/joyehuang/skills/tree/main/diff-story
Command: npx skills add https://github.com/joyehuang/skills --skill diff-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of documenting development progress by automatically transforming raw git diffs into structured, human-readable technical stories that explain the 'why' behind code changes.

Core Features & Use Cases

  • Narrative Generation: Converts commit history into a coherent story covering background, discovery, analysis, and implementation.
  • Derivative Outputs: Automatically generates PR descriptions, resume bullet points, and blog post outlines from your work.
  • Use Case: After finishing a complex feature or bug fix, use this skill to generate a professional summary for your team's PR or your personal portfolio.

Quick Start

Ask the diff-story skill to generate a technical narrative for the changes made in the current branch.

Frequently Asked Questions about diff-story

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

FAQPage Schema
How do I generate a technical narrative from my git commit history?

To generate a technical narrative from your git commit history, you can use a tool that analyzes branch history and file-level modifications to produce structured, human-readable stories. This converts raw diffs into documentation explaining the context behind code changes.

Can I automatically create PR descriptions from git diffs?

Yes, you can automatically create PR descriptions from git diffs by analyzing commit history to extract the background, discovery, analysis, and implementation phases of your work. This translates code modifications into a professional summary for your team's pull request.

Does generating a git diff narrative require CLI access?

Generating a git diff narrative requires git CLI access to interpret branch history and file-level modifications accurately. This access allows the narrative generation process to read your raw code changes and transform them into structured technical stories for your workflow.

What is the best way to document development progress for a resume?

The best way to document development progress for a resume is to transform complex feature implementations or bug fixes into structured bullet points. By analyzing git commit history and diffs, you can automatically generate derivative outputs like resume content that highlights your technical contributions.

How do I turn a complex feature implementation into a blog post outline?

To turn a complex feature implementation into a blog post outline, you can analyze the git commit history to construct a coherent story covering the discovery, analysis, and implementation phases. This narrative generation automatically produces structured outlines for technical documentation.