pr

Create pull requests from feature branches using conventional commit format.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/MediTracer/mobius --skill pr-meditracer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/MediTracer/mobius/tree/main/.opencode/skills/pr
Command: npx skills add https://github.com/MediTracer/mobius --skill pr-meditracer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually drafting pull requests is time-consuming and error-prone, especially when aligning with conventional commits and issue references; this skill automates PR creation to streamline code reviews and release processes.

Core Features & Use Cases

  • Auto-detect issue references from branch names and commits
  • Generate PR titles following the conventional commit format and assemble a rich body with contexts
  • Create PRs via GitHub CLI without interactive prompts
  • Output structured linking data for mobius to attach PRs to Linear/Jira issues

Quick Start

Run the pr skill on your current branch to auto-create a PR.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate pull request creation from a branch without interactive prompts?

Automating pull request creation is achieved by detecting issue references from branch names and commits, then generating a conventional commit PR title and body via the gh CLI without interactive prompts.

How does conventional commit format work when auto-generating pull requests?

Conventional commit format structures the auto-generated PR title to align with your release process, while the skill assembles a rich PR body using context extracted from your branch and commit history.

Can I link an auto-created GitHub pull request to a Linear or Jira issue?

Linking an auto-created pull request to Linear or Jira is supported by outputting structured data designed for mobius to attach the PR to the corresponding issue automatically.

How do I auto-detect issue references from branch names and commits for a PR?

Auto-detecting issue references works by parsing your branch name and commit history, extracting the relevant ticket identifiers to include in the generated pull request body and linking data.

Does the GitHub CLI support non-interactively creating pull requests from feature branches?

The GitHub CLI supports non-interactively creating pull requests from feature branches by executing gh pr create with auto-generated conventional commit titles and contextual bodies.

Why manually draft pull requests when you can auto-generate PR titles and bodies from commit history?

Manually drafting pull requests is time-consuming and error-prone; auto-generating PR titles and bodies from commit history streamlines code reviews and ensures conventional commit alignment.