generate-pr-description

To generate a standardized Chinese PR description from a git diff, the Skill parses your diff output to identify core functional changes and structures them into a Problem, Solution, and Test Plan format. This ensures concise summaries for code reviewers.

The generated pull request description follows a strict three-part format: Problem, Solution, and Test Plan. The Solution section uses unordered lists or subheadings, while the Test Plan uses ordered steps to ensure output consistency and executable verification.

Yes, you can use this for feature branch merges. It applies to software engineering workflows where developers prepare pull requests across feature and main/master branches, generating concise, standardized Chinese summaries for reviewers to quickly locate key changes.

No, the generated PR description does not support emoji or English text. It enforces strict language and format constraints by outputting Chinese only and prohibiting emoji to maintain a clean, professional, and standardized code review context.

You need a structured Test Plan in your pull request description to provide actionable test steps derived from the git diff. This helps reviewers understand the implementation solution and efficiently verify that the core functional changes work as intended.