git-commit-push-pr

To generate a pull request description, the Skill analyzes your git commit history and working changes to produce value-driven summaries. It scales the description length based on change complexity and branch context, ensuring reviewers understand the impact without manual drafting.

Yes, you can update an existing PR description by requesting a rewrite. The Skill refreshes the context and evidence while preserving existing evidence blocks where present, ensuring your pull request consistently reflects the latest work and reasoning.

Writing a PR description that scales with change complexity requires evaluating the branch context and technical impact. This Skill generates adaptive descriptions that align with conventional commit conventions, applying clear value-first narration for both small fixes and complex features.

Yes, this PR description generator works with conventional commit workflows by following conventional commit-oriented conventions when possible. It aligns your commit and push workflows to ensure pull requests consistently reflect the latest work and technical reasoning.

The best way to automate PR description creation for code review is using a Skill that parses working changes and generates value-first narration. It eliminates manual drafting, preserves existing evidence blocks, and communicates user-facing impact to reviewers.

You should not use automated PR description generation when your changes lack clear commit context or require highly customized, non-conventional formatting. The Skill follows conventional commit-oriented conventions and preserves existing evidence blocks, so highly irregular workflows may not yield optimal descriptions.