Create PR Description

Overview

Generate a comprehensive, reviewer-friendly pull request description by analyzing staged git changes, commit history, and project conventions. The output is a ready-to-paste PR body that explains the "why" behind every change.

Workflow

1. Read project context — Check for .chalk/docs/engineering/ files, especially PR conventions, coding style, and architecture docs. If a conventions file exists, follow its PR template. If not, use the default structure below.

2. Gather git context — Run these commands to understand the change:

   • git diff --cached --stat for an overview of changed files
   • git diff --cached for the full staged diff
   • git log --oneline -10 for recent commit context
   • git branch --show-current for the branch name
   • If $ARGUMENTS contains an issue number, read the issue details if accessible

3. Analyze the diff — Before writing anything, categorize the changes:

   • Identify the primary intent (feature, bugfix, refactor, chore, docs)