branch-pr

Creates GitHub pull requests with issue linkage, branch naming, and label validation.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill branch-pr-zmynxx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-pr
Source: https://github.com/zMynxx/bifrost-with-opencode/tree/main/.opencode/skills/branch-pr
Command: npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill branch-pr-zmynxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributors often open pull requests that lack linked issues, proper labels, or conventional commit formatting, causing automated CI checks to fail and slowing down review cycles. This Skill enforces the full PR workflow so every submission passes validation on the first attempt. ## Core Features & Use Cases - Issue-First Validation: Verifies the linked issue carries the status:approved label before any PR is opened, blocking blank or unlinked PRs. - Branch Naming & Commit Enforcement: Applies the type/description branch regex and conventional commit format (type(scope): description) with a type-to-label mapping table. - Structured PR Body: Generates the required PR template sections including linked issue, type checkbox, summary, changes table, test plan, and contributor checklist. - Use Case: A contributor finishes a bug fix and asks the assistant to open a PR; the Skill creates a fix/zsh-glob-error branch, runs shellcheck, opens the PR with Closes #42, and adds the type:bug label so all GitHub Actions checks pass. ## Quick Start Ask the assistant to create a pull request for the current changes linked to approved issue number 42.

Frequently Asked Questions about branch-pr

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

FAQPage Schema
How do I create a pull request that passes automated validation checks?▼

Link an approved issue using Closes #N in the PR body, add exactly one type:* label, and follow the required template sections. The PR Validation workflow checks the issue reference, its status:approved label, and the PR label before merge is possible.

What branch naming format is required for pull requests?▼

Branches must match the pattern type/description, such as feat/user-login or fix/zsh-glob-error. The type must be one of feat, fix, chore, docs, style, refactor, perf, test, build, ci, or revert, with lowercase descriptions using only a-z, 0-9, dots, underscores, and hyphens.

Why was my pull request blocked by GitHub Actions?▼

PRs are blocked when the body lacks a Closes/Fixes/Resolves #N keyword, the linked issue is missing the status:approved label, or the PR has zero or multiple type:* labels. Shell scripts must also pass shellcheck in the CI job.

What commit message format does conventional commits require?▼

Commits must follow type(scope): description, where type is one of build, chore, ci, docs, feat, fix, perf, refactor, revert, style, or test. An optional exclamation mark before the colon indicates a breaking change, mapping to the type:breaking-change label.

Can I open a pull request without a linked issue?▼

No. Every PR must link an issue with the status:approved label using Closes, Fixes, or Resolves keywords. Blank PRs without issue linkage are automatically blocked by the PR validation workflow.