What problem does it solve? Opening a pull request involves repetitive, error-prone steps: checking for existing PRs, reviewing the full branch diff, choosing a conventional-commit title, and writing a structured body. This Skill standardizes that workflow so every PR is reviewed, correctly titled for auto-semver release notes, and consistently formatted. ## Core Features & Use Cases - Existing-PR detection: Runs gh pr list before creating anything, preventing duplicate PRs and optionally refreshing a stale PR body via gh pr edit. - PR-tier review gate: Requires a clean reviewer verdict (project reviewer or the ankyr-review plugin) before the PR is opened. - Conventional titles and templated bodies: Selects a feat:/fix:-style prefix from title conventions and builds a Summary + Test plan body from the PR template, omitting empty sections. - Use Case: After finishing a feature branch, ask the agent to open a PR; it inspects the full merge-base...HEAD diff, reviews the changes, picks feat: add OAuth login flow, and creates the PR with grouped Summary sections and a checklist test plan. ## Quick Start Ask the agent to create a pull request for the current branch against the base branch defined in AGENT.md.
