branch-pr

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributors often open pull requests that fail automated CI checks because they lack a linked approved issue, use invalid branch names, or miss the required type label. This Skill enforces the full PR workflow so submissions pass validation on the first attempt. ## Core Features & Use Cases - Issue-first PR creation: Verifies the linked issue carries the status:approved label and requires a Closes #N / Fixes #N / Resolves #N reference in the PR body. - Branch and commit conventions: Enforces the type/description branch naming regex and Conventional Commits format (type(scope): description) with a type-to-label mapping table. - PR body structure: Guides the required sections — linked issue, exactly one type:* label, summary, changes table, test plan, and contributor checklist — plus shellcheck runs on modified scripts. - Use Case: A contributor fixing a shell script bug asks the assistant to prepare the PR; the Skill creates fix/zsh-glob-error, runs shellcheck, opens the PR with Closes #42, and adds the type:bug label. ## Quick Start Create a pull request for issue 42 following the branch naming, commit, and label rules.

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 with Closes #N in the PR body, add exactly one type:* label, and follow the PR template sections. The GitHub Actions checks verify the issue reference, the status:approved label, and the type label before merge is possible.

What branch naming convention should I use for pull requests?▼

Use the format type/description, such as feat/user-login or fix/zsh-glob-error. The name must match the regex ^(feat|fix|chore|docs|style|refactor|perf|test|build|ci|revert)/[a-z0-9._-]+$ with lowercase and no spaces.

Why was my pull request blocked by GitHub Actions?▼

PRs are blocked when the body lacks a Closes/Fixes/Resolves #N reference, the linked issue is missing the status:approved label, or the PR does not have exactly one type:* label. Blank PRs without issue linkage are always rejected.

How do conventional commit messages map to PR labels?▼

Each commit type maps to a label: feat to type:feature, fix to type:bug, docs to type:docs, refactor to type:refactor, and chore/style/test/build/ci to type:chore. Breaking changes marked with ! map to type:breaking-change.

Do I need to run shellcheck before opening a pull request?▼

Yes, run shellcheck on all modified shell scripts before pushing, since the CI Shellcheck job must pass. The contributor checklist in the PR template requires confirming scripts run without errors.