pr-writer

To create a pull request with conventional commit titles, draft a structured title and body following conventional commit rules, then execute gh pr create via GitHub CLI. This enforces consistent PR documentation and standardized review context across collaborative repositories.

A structured pull request description must define what the change does, why it is needed, alternatives considered, and reviewer context. It deliberately excludes test plan checklists and redundant summaries to maintain disciplined, focused PR documentation.

Yes, a clean, rebased branch state is required before opening a pull request. Branch validation leverages git status, git log, and gh repo view commands to confirm readiness, ensuring PRs land without undocumented changes or merge conflicts.

Updating an existing GitHub pull request body and title requires running gh api update commands after composing conventional commit-compliant text. This modifies documented intent and reviewer context on open PRs without creating new pull requests.

Yes, GitHub CLI authenticated access is required for this pull request creation workflow. It leverages gh pr create and gh api commands to draft, edit, or finalize PRs while enforcing conventional commit conventions and documented description structures.

Limitations of enforcing conventional commits on pull requests include the exclusion of test plan checklists and redundant summaries, focusing strictly on documented intent. It also requires manual guidance for drafting titles and descriptions rather than fully automating PR generation.