What problem does it solve? Turning finished branch work into a properly formed pull request involves many error-prone steps: detecting the forge, resolving the base branch, committing and pushing leftover changes, avoiding duplicate PRs, assigning milestones, and optionally merging. This Skill automates that entire flow while delegating git mechanics to dedicated commit and branch skills. ## Core Features & Use Cases - Forge-aware PR creation: Detects GitHub vs Gitea from project configuration and uses the matching scripts or MCP tools, always passing owner/repo explicitly. - Delegated git mechanics: Commits and pushes uncommitted work via the make-commit skill and creates branches via create-branch, never reimplementing git logic. - Duplicate and safety guards: Verifies no open PR already exists for the head branch, requires explicit prompt consent before merging, and escalates on conflicts or missing configuration. - Use Case: After implementing an issue on a feature branch, invoke the skill to commit remaining changes, open a PR titled feat(api): add retry logic with Closes #42, assign the current milestone, and optionally squash-merge when the prompt authorized it. ## Quick Start Ask the assistant to open a pull request for the current branch, optionally naming the base branch, issue number, or milestone.