pr-description

To generate a PR description from a git diff, provide the diff or branch name to analyze change context, extract rationale from commits, and assemble a complete PR body aligned with the repository's PR template.

Automate filling out a GitHub pull request template by analyzing git diffs, branch names, and commit messages to populate sections like Description, Changelog, Related issues, and manual testing steps.

The best way to write a PR changelog entry and manual testing steps is to extract impact and context directly from code changes, ensuring the generated PR body passes readiness checks and preserves the official template structure.

Yes, you can use branch names and commit messages to locate related issues, as the PR description generation process analyzes this context to derive rationale and automatically link relevant issues within the PR template.

Yes, automated PR description generation works with custom repository PR templates by identifying the change context and assembling the PR template sections to ensure the final description preserves the official template structure.

Generated PR descriptions may fail readiness checks if the analyzed git diff lacks sufficient context, but the template assembly process is designed to automatically include manual testing steps and a changelog entry to ensure readiness.