skills.rest
Garsson-io
Garsson-ioOFFICIAL
Explore all skills by this author →
GitHub

kaizen-write-pr

Generate PR descriptions using the Story Spine narrative with structured sections.

Updated Mar 16, 2026
Search Tags:#software-engineering#kaizen#pull-request#pr-description#narrative-writing#story-spine
One-click install
npx skills add https://github.com/Garsson-io/kaizen --skill kaizen-write-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kaizen-write-pr
Source: https://github.com/Garsson-io/kaizen/tree/main/.agents/skills/kaizen-write-pr
Command: npx skills add https://github.com/Garsson-io/kaizen --skill kaizen-write-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR descriptions are often verbose, unfocused, or missing rationale. This Skill generates clear, narrative PR bodies to help reviewers understand the problem, approach, evidence, and impact without reading diffs.

Core Features & Use Cases

  • Story Spine-driven PR bodies: follows the arc (Once upon a time... through And ever since...) to frame the change.
  • Structured sections: architecture, design decisions, what’s in this PR, validation, known limitations, and how the change closes linked issues.
  • Evidence & test plan: guides gathering real-world evidence and links to test plans to ensure acceptance criteria are met.

Quick Start

Provide a PR body that follows the Story Spine narrative for the current branch.

Frequently Asked Questions about kaizen-write-pr

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

FAQPage Schema
How do I write a pull request description that explains the problem and solution clearly?▼

A pull request description should use a Story Spine narrative to explain the change, framing the problem, discovery, solution, evidence, and impact so reviewers understand the context without reading diffs.

What should a PR description include for software engineering review?▼

A PR description should include an architecture diagram, design decisions table, file changes table, validation checklist with concrete results, known limitations, and mandatory linkage to the issue's acceptance criteria and test plan.

How do I link an issue's acceptance criteria to a pull request?▼

Linking acceptance criteria to a pull request requires enforcing mandatory issue linkage and scope matching, explicitly referencing the linked issue's test plan and acceptance criteria within the PR body's validation checklist.

How do I structure a PR validation checklist with concrete evidence?▼

A PR validation checklist should gather real-world evidence and reference linked test plans, ensuring that each item maps directly to the issue's acceptance criteria and demonstrates concrete validation results.

What is the best way to document design decisions in a pull request?▼

Documenting design decisions in a pull request is best achieved using a structured design decisions table, placed alongside the Story Spine narrative to clarify the rationale behind the chosen solution.

When should I include known limitations in a PR description?▼

Known limitations should be included in a PR description whenever the change has scope constraints or unresolved edge cases, ensuring reviewers understand the boundaries of the solution and its current impact.

Related Skills

Explore More Software Engineering Skills→
paulinghampaulingham
1

changelog

Generate a PR narrative and Keep-a-Changelog entry from a git diff and acceptance criteria.

Community
Advanced
diShine-digital-agencydiShine-digital-agency
1

shine-ship

Automate the ship cycle from branch creation to merged pull request.

Community
Intermediate
prof-danielcprof-danielc

speckit.checker

Run static analysis tools and aggregate results into a prioritized issue report.

Community
Advanced
adrielpadrielp
20

pr_description_generator

Generate Markdown pull request descriptions from repository templates using Gemini CLI.

Community
Advanced