skills.rest
etrigan16
etrigan16COMMUNITY
Explore all skills by this author →
GitHub

branch-pr

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

Updated May 24, 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/etrigan16/v0-cipher-ar --skill branch-pr-etrigan16
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-pr
Source: https://github.com/etrigan16/v0-cipher-ar/tree/main/.opencode/skills/branch-pr
Command: npx skills add https://github.com/etrigan16/v0-cipher-ar --skill branch-pr-etrigan16

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Opening pull requests that fail repository automation wastes contributor time. This Skill enforces the full PR workflow—approved issue linkage, conventional branch naming, type labels, and passing checks—so every PR meets the repository's GitHub Actions validation rules on the first attempt. ## Core Features & Use Cases - Issue-First Validation: Verifies the linked issue carries the status:approved label and that the PR body contains a Closes #N keyword before submission. - Branch and Commit Conventions: Enforces the type/description branch regex and conventional commit format (type(scope): description) with a type-to-label mapping table. - PR Template Compliance: Structures the PR body with linked issue, type checkbox, summary, changes table, test plan, and contributor checklist, then adds exactly one type:* label. - Use Case: A contributor fixing a shell script bug runs this Skill to create branch fix/zsh-glob-error, run shellcheck, open a PR with Closes #42, and apply the type:bug label so all automated 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 PR template sections. The GitHub Actions workflow verifies 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, 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, such as feat/user-login.

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. Blank PRs without issue linkage are always rejected.

How do conventional commits 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 Check Issue Reference and Check Issue Has status:approved jobs in the PR validation workflow will block any PR missing this linkage.

Related Skills

Explore More Software Engineering Skills→
JNZaderJNZader

issue-creation

Enforces GitHub issue templates, statuses, and approval workflow for Agent Teams Lite.

Community
Intermediate
bitpantrybitpantry

finish-pr

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

Community
Advanced
d-oitd-oit
13

shell-script-quality

Lint shell scripts with ShellCheck and run BATS test suites.

Community
Intermediate
wahidyankfwahidyankf
3

repo-practicing-trunk-based-development

Enforce small, frequent commits to the main branch for Trunk Based Development workflows.

Community
Advanced