skills.rest
PixelDroid19
PixelDroid19COMMUNITY
Explore all skills by this author →
GitHub

branch-pr

Create branches and open PRs with issue linkage and type labels.

Updated Aug 23, 2026
Search Tags:#git#branch#ci#pull-request#conventional-commits#issue-tracker
One-click install
npx skills add https://github.com/PixelDroid19/cells-agents --skill branch-pr-pixeldroid19
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-pr
Source: https://github.com/PixelDroid19/cells-agents/tree/main/skills/branch-pr
Command: npx skills add https://github.com/PixelDroid19/cells-agents --skill branch-pr-pixeldroid19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a branch and pull request workflow that enforces issue linkage, a single type label, and CI validation to streamline collaboration and governance.

Core Features & Use Cases

  • Enforce mandatory issue linkage for every PR.
  • Require exactly one type:* label to standardize PR categorization.
  • Provide a repeatable branch naming convention and PR template to accelerate contribution.

Quick Start

Create a new branch for issue #123 with a feature-type PR and open a PR using the template.

Frequently Asked Questions about branch-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce issue linkage when opening a pull request?▼

To enforce issue linkage when opening a pull request, you need an automated workflow that mandates referencing a specific issue before branch creation. This ensures every contribution traces back to an issue tracker entry for streamlined governance.

What is the best way to standardize PR categorization with conventional commits?▼

Standardizing PR categorization with conventional commits requires applying exactly one type-based label to each pull request. This standardizes categorization and aligns with a conventional-commits workflow to streamline collaboration across contributors.

How do I automate branch creation for issue-first workflows?▼

Automating branch creation for issue-first workflows requires applying a type-based branch naming pattern tied to an issue tracker ID. This generates repeatable branch names and accelerates contribution while maintaining project governance standards.

Do I need a PR template to pass CI checks in collaborative software projects?▼

You need a PR template to pass CI checks in collaborative software projects because it ensures compliant submissions. Combining the template with mandatory issue linkage and a single type label enforces the validation needed to streamline collaboration.

Can I use type labels without a conventional-commits workflow?▼

Type labels should not be used without a conventional-commits workflow because the PR categorization relies on this structure. The automated branch and PR workflow requires conventional commits to ensure compliant, properly categorized submissions.

Related Skills

Explore More Software Engineering Skills→
lleontor705lleontor705
1

open-pr

Enforce issue-first governance and type labels on GitHub pull requests.

Community
Advanced
maxculen86maxculen86

branch-pr

Enforce issue linkage and single type labels on GitHub pull requests.

Community
Intermediate
nseluganseluga

triage

Automate issue triage and pull request management with structured agent briefs.

Community
Intermediate
etylsarinetylsarin
59

git-workflow

Enforce feature-branch pull request workflows and prevent direct commits to main.

Community
Intermediate