skills.rest
albersg
albersgCOMMUNITY
Explore all skills by this author →
GitHub

branch-pr

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

Updated Mar 7, 2026
Search Tags:#code review#pull request#conventional commits#github#shellcheck#branch naming#contribution workflow
One-click install
npx skills add https://github.com/albersg/dotfiles --skill branch-pr-albersg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-pr
Source: https://github.com/albersg/dotfiles/tree/main/dotfiles-opencode/.opencode/skills/branch-pr
Command: npx skills add https://github.com/albersg/dotfiles --skill branch-pr-albersg

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 Gentle AI contribution workflow so every PR passes validation on the first attempt. ## Core Features & Use Cases - Issue-First Enforcement: Verifies the linked issue carries the status:approved label and requires Closes #N keywords in the PR body. - Branch and Commit Conventions: Validates branch names against the type/description regex and enforces conventional commit messages with type-to-label mapping. - PR Template Compliance: Guides the full PR body structure including summary, changes table, test plan, and contributor checklist, plus shellcheck runs on modified scripts. - Use Case: A contributor fixing a shell script bug creates a fix/zsh-glob-error branch, commits with fix(scripts): correct glob handling, and opens a PR with the type:bug label that passes all GitHub Actions checks. ## 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 PR template sections. Run shellcheck on modified scripts before pushing so the CI Shellcheck job passes.

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

Branch names must match the pattern type/description, where type is one of feat, fix, chore, docs, style, refactor, perf, test, build, ci, or revert. The description must be lowercase 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 reference, the linked issue is missing the status:approved label, or the PR has zero or multiple type:* labels. Fix the failing check and the validation job will pass.

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.

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.

Related Skills

Explore More Software Engineering Skills→
etrigan16etrigan16

issue-creation

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

Community
Intermediate
badbsallyybadbsallyy

prepare-pr

Rebase a GitHub pull request onto main and run automated checks.

Community
Advanced
CalmKernelTRCalmKernelTR
7

Shell Lint ve Test

Lint and test Bash projects with ShellCheck, shfmt, and BATS.

Official
Advanced
modu-aimodu-ai
4

moai-ref-git-workflow

Standardize Git workflows, branch strategies, and PR templates across projects.

Official
Advanced