pr-description-writing

Drafting a Shopware pull request description involves detecting the feature branch state and diff to generate a conventional commit title and a 5-section description covering Why, What, How to Reproduce, and References.

The conventional commit format for PR titles structures the change type and scope directly from the branch analysis, producing a standardized title that clearly communicates the modification context for Shopware projects.

Generating a PR title from a feature branch diff requires analyzing the changes against the trunk branch, detecting the modification scope, and formatting the result into a conventional commit title.

Yes, the Shopware PR description template includes a How to Reproduce section to provide testing and verification instructions for the submitted changes, ensuring reviewers can validate the modifications.

Automating Shopware pull request drafting is best achieved through a phase-driven workflow that detects the branch state, analyzes the diff, gathers missing context, and enforces Shopware writing guidelines and anti-slop rules.

Your PR description may be rejected for violating Shopware writing guidelines or anti-slop rules, which require a specific 5-section template and conventional commit formatting that can be enforced during the drafting phase.