open-pr

Opens a pull request on GitHub or Gitea with Conventional Commits title and issue linkage.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/sagittaras/agentic-workflow --skill open-pr-sagittaras
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/sagittaras/agentic-workflow/tree/main/skills/open-pr
Command: npx skills add https://github.com/sagittaras/agentic-workflow --skill open-pr-sagittaras

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about open-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I open a pull request from the current branch automatically?

Invoke the skill with an optional base branch, issue number, or milestone. It detects the forge, commits and pushes any uncommitted work through the make-commit skill, then creates the PR with a Conventional Commits title and a body linking the closed issue.

Does this skill support both GitHub and Gitea pull requests?

Yes. The forge type is read from the project configuration's Forge section. GitHub uses bundled gh wrapper scripts with an explicit -R owner/repo argument, while Gitea uses MCP pull request tools loaded via ToolSearch.

Can the skill merge the pull request after creating it?

Only when the prompt that started the run contains an explicit merge consent phrase such as asking to merge directly. Without that consent the PR stays open; with it, the skill performs a squash merge and deletes the source branch.

What happens if a pull request already exists for my branch?

The skill lists open PRs and compares head branch names before creating anything. If a matching PR exists with the same base branch, it returns that PR instead of creating a duplicate; a mismatched base triggers escalation.

Why does the skill stop when project configuration is missing?

The Forge and Branching sections in CONTRIBUTING.md define which forge recipes and default branch to use. Without them the skill cannot determine where the PR should target, so it stops and suggests running init-workflow instead of guessing.