create-pr-description

To generate a pull request description, this Skill reads your staged git changes and commit messages to output a structured PR body explaining the rationale behind each modification. It automatically extracts the changed files and composes a ready-to-paste PR description.

Yes, PR documentation can include issue numbers and project conventions. The Skill optionally applies your project conventions and supports the inclusion of issue references to ensure the generated pull request description aligns with your codebase standards.

Automating code review rationale is best handled by extracting commit messages and changed files from staged git changes. The Skill composes a structured pull request body that communicates the 'why' behind each change, saving time during documentation and review.

The PR generator works across any standard git codebase without requiring specific dependencies. It reads the git context directly to analyze staged changes, making it suitable for diverse repositories and various pull request workflows.

To create a ready-to-paste PR body, simply ask the Skill to generate a description from your currently staged files. It processes the staged git changes and outputs structured text formatted for immediate use in GitHub pull requests.