skills.rest
AD-Paladins
AD-PaladinsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

branch-pr

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

Updated Jul 10, 2026
Search Tags:#code review#pull request#git workflow#conventional commits#github#branch naming#ci validation
One-click install
npx skills add https://github.com/AD-Paladins/beaconator-web --skill branch-pr-ad-paladins
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-pr
Source: https://github.com/AD-Paladins/beaconator-web/tree/main/.config/opencode/skills/branch-pr
Command: npx skills add https://github.com/AD-Paladins/beaconator-web --skill branch-pr-ad-paladins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributors often open pull requests that fail automated 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 Validation: Verifies the linked issue carries the status:approved label before any PR is opened, preventing blocked submissions. - Branch Naming Enforcement: Generates branch names matching the type/description regex (feat, fix, chore, docs, and more) so CI branch validation passes. - Conventional Commits & Labels: Maps commit message types to the correct type:* PR label and structures the PR body with linked issue, summary, changes table, and test plan. - Use Case: A contributor fixing a shell script bug runs this Skill to create fix/zsh-glob-error, commit with fix(scripts): correct glob handling, and open a PR with Closes #42 plus the type:bug label that passes all GitHub Actions checks. ## Quick Start Ask the assistant to create a pull request for issue number 42 following the branch naming and labeling 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 using Closes #N in the PR body, add exactly one type:* label, and use a branch named type/description. Run shellcheck on modified scripts before pushing so the CI Shellcheck job passes.

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

Use the format type/description where type is one of feat, fix, chore, docs, style, refactor, perf, test, build, ci, or revert. The description must be lowercase and contain 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 reference, the linked issue is missing the status:approved label, or the PR has zero or multiple type:* labels. Check the PR Validation job output to identify which check failed.

How do conventional commit types 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.

Can I open a pull request without linking an issue?▼

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

Related Skills

Explore More Software Engineering Skills→
albersgalbersg

issue-creation

Creates GitHub issues using bug report and feature request templates with label workflows.

Community
Intermediate
bitpantrybitpantry

finish-pr

Merge reviewed GitHub pull requests after tests pass and branches sync.

Community
Advanced
pecorapromotionsllc-cellpecorapromotionsllc-cell

ci-cd-and-automation

Run lint, type checks, tests, builds, and security audits on GitHub Actions.

Community
Advanced
pekralpekral

pr-summary

Generate concise pull request change summaries from git commits.

Community
Intermediate