create-pr

To write a pull request description with clear scope, generate a concise summary covering the scope of changes, rationale, and impact. Enforce inclusion of explicit validation steps and rollout notes suitable for CI workflows and code reviews.

PR rollout notes for CI workflows must include explicit validation steps and deployment instructions. These notes ensure smooth code reviews and testing by clarifying the rationale and impact of feature, bugfix, or refactor changes.

Generating PR descriptions for multi-commit feature branches requires aggregating commits into a concise, targeted overview. The description must enforce explicit scope, validation steps, and rollout notes suitable for the code review process.

Yes, this PR generation approach applies to bugfix and refactor scenarios across single- and multi-commit workflows. It generates concise descriptions that clearly articulate the scope, rationale, and impact of the code changes for review.

Vague pull request descriptions are problematic because they omit critical scope, validation, and rollout notes. This lack of clarity leads to unclear changes and extended review cycles, delaying the deployment of features and bugfixes.