craft-pr

Generates a Markdown PR description from task files and git diff.

31|6|Updated Feb 26, 2026

Search Tags:#automation #diff #tasks #branch #pr #description #pull-request

Ready to run

npx skills add https://github.com/nickmaglowsch/claude-setup --skill craft-pr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: craft-pr
Source: https://github.com/nickmaglowsch/claude-setup/tree/main/.claude/skills/craft-pr
Command: npx skills add https://github.com/nickmaglowsch/claude-setup --skill craft-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reads task files from tasks/<branch>/ and the diff against origin/main to generate a polished PR description in markdown for the user to copy-paste.

Core Features & Use Cases

Reads per-branch task files to extract scope and intent.
Compares with diff against origin/main to summarize changes.
Produces a ready-to-paste PR description in markdown for reviewers.

Quick Start

Run the craft-pr skill on your feature branch to generate a ready-to-paste PR description, then paste it into the PR body.

Frequently Asked Questions about craft-pr

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

FAQPage Schema

How do I generate a pull request description from a git diff?▼

You can generate a pull request description by reading per-branch task files and comparing the branch diff against origin/main to produce a polished markdown summary of the changes and rationale.

What is the best way to summarize feature branch changes for reviewers?▼

The best way to summarize feature branch changes is to compare per-branch task files against the origin/main diff, producing a ready-to-paste markdown PR description that captures the scope, changes, and intent for reviewers.

Do I need task files in my repository to automate PR descriptions?▼

Yes, you need task files located in tasks/<branch>/ within your git repository, as the tool reads these files to extract the scope and intent required to generate the markdown PR description.

Can I use branch task files to generate a markdown PR body?▼

Yes, you can use branch task files by comparing them to the origin/main diff to generate a ready-to-paste markdown PR body that outlines the work, changes, and rationale for code reviewers.

Does generating a PR description from diffs work without external dependencies?▼

Generating a PR description from diffs works without external dependencies, requiring only local access to the git repository to read task files and compare the branch diff against origin/main.