skills.rest
Balthael
BalthaelCOMMUNITY
Explore all skills by this author →
GitHub

branch-pr

Guides pull request creation with issue linkage, branch naming, and label enforcement.

Updated Apr 10, 2026
Search Tags:#code review#pull request#conventional commits#github#issue tracking#branch naming#ci validation
One-click install
npx skills add https://github.com/Balthael/ciberbal-ai --skill branch-pr-balthael
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-pr
Source: https://github.com/Balthael/ciberbal-ai/tree/main/internal/assets/skills/branch-pr
Command: npx skills add https://github.com/Balthael/ciberbal-ai --skill branch-pr-balthael

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 blocking merges. This Skill enforces the issue-first PR workflow so every submission 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 Naming Validation: Enforces the type/description regex pattern (e.g., feat/user-login, fix/zsh-glob-error) across 11 branch types. - Label and Commit Mapping: Maps conventional commit types to exactly one type:* PR label and lists the automated checks that must pass. - Use Case: A contributor fixing a shell script bug creates branch fix/zsh-glob-error, commits with fix(scripts): handle glob expansion, runs shellcheck, and opens a PR with Closes #42 and the type:bug label so all GitHub Actions checks pass. ## Quick Start Ask the agent to create a pull request for the approved issue you are working on, 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?▼

Link an approved issue using Closes #N in the PR body, add exactly one type:* label matching your change, and ensure shellcheck passes on modified scripts. All GitHub Actions checks must pass 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 type must be one of feat, fix, chore, docs, style, refactor, perf, test, build, ci, or revert, and 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. Blank PRs without issue linkage are always rejected.

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 a linked issue?▼

No. Every PR must link an approved issue with no exceptions. The linked issue must carry the status:approved label, and the PR body must include a valid closing keyword like Closes #N.

Related Skills

Explore More Software Engineering Skills→
zMynxxzMynxx

issue-creation

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

Community
Intermediate
ZaxbyHubZaxbyHub
437

swarm-pr-feedback

Resolve pull request feedback with verified source evidence and closure summaries.

Official
Advanced
d-o-hubd-o-hub
4

shell-script-quality

Enforce ShellCheck linting and BATS test coverage for shell scripts.

Community
Intermediate
Scheune10-codingScheune10-coding

git-workflow

Enforce Git branching, commit, and release workflows with validation.

Community
Advanced