Generate two-column PR walkthroughs with prose narrative and comprehensive code map.
npx skills add https://github.com/love-lena/skills --skill change-story-love-lena
Please help me install this Agent Skill. Skill: change-story Source: https://github.com/love-lena/skills/tree/main/skills/change-story Command: npx skills add https://github.com/love-lena/skills --skill change-story-love-lena
prose.md (a continuous narrative naming consequences), map.md (every hunk in the diff grouped by surface with framing paragraphs), and diff.patch (the verbatim unified diff). - Chip cross-linking: Inline line-range markdown links in the prose point directly at hunks in the map, so readers can jump from a consequence to the exact mechanics. - Coverage audit: A built-in audit checklist verifies every + line in the diff is covered by a map fence and that addition/deletion totals match the change header. - Use Case: You have a 6-PR stack touching 40 files. Run this Skill to produce a walkthrough where reviewers read a short prose chapter for the story and consult the map for every hunk, instead of scrolling a fragmented diff view. ## Quick Start Generate a change story for the current pull request using its diff, title, and description.High-intent search queries and answers about installing and using this skill.
Provide the unified diff (from git diff or gh pr diff), the PR title, and description. The Skill writes map.md first with every hunk grouped by surface, then prose.md as a short narrative with chip links pointing at line ranges in the map.
A change story is a two-column walkthrough of a code change: a continuous prose chapter naming what changed and why on the left, and a surface-grouped code map covering every diff hunk on the right. It outputs three markdown artifacts: prose.md, map.md, and diff.patch.
Yes, stacked PRs are a primary use case. Provide the combined diff across the stack's commits, and the map groups hunks by surface rather than by PR number, so related changes across PRs appear together.
Yes. The three output files are plain markdown and readable on their own. A renderer that understands the chip-and-fence convention can additionally lay them out as a two-column page with expandable hunks.
The prose must be grounded in the diff; PR body claims not visible in the diff are quoted as evidence or marked [NEEDS INFO]. The Skill instructs narrowing scope rather than inventing causation when the reasoning behind a change cannot be determined.
hackberrybayGenerate a structured PR title and description from branch diffs.
baobao0303Review prose for communication issues and output a three-column table.
Sir-chawakornAutomate Pull Request reviews for code quality, security, and performance.
prismaGenerate GitHub pull requests with conventional commit titles and narrative descriptions.