pr

You can generate a pull request from existing commits by providing your repository's commit history. The skill analyzes the commits to craft a clear, ready-to-submit PR draft, extracting intent and rationale to produce titles and bodies without pushing new changes.

The best way to write a PR body aligned with project conventions is to use an automated skill that analyzes commit history to compose detailed descriptions. It aligns the generated change explanations and testing notes with reviewer expectations across repositories.

Yes, you can automate PR title and body generation without adding new commits. The skill works by analyzing existing commit history on your branch to extract change scope and impact, generating PR-ready metadata without introducing pushes or branch changes.

Analyzing commit history improves code review preparation by extracting intent, changes, and rationale from past commits. It transforms these details into actionable pull request descriptions and reviewer-facing rationale, ensuring the PR clearly communicates the scope and impact of the changes.

This PR generation workflow does not require specific branch configuration, but it applies to workflows where PRs are created from existing commits or branches. You simply provide the commit history, and no new commits, pushes, or branch changes are introduced during generation.