skills.rest
AlejandroFerp
AlejandroFerpCOMMUNITY
Explore all skills by this author →
GitHub

branch-pr

Enforce issue linkage and single type:* labels on GitHub PRs.

Updated Apr 20, 2026
Search Tags:#git#workflow#github#branch#pull-request#branch-naming#pr-review
One-click install
npx skills add https://github.com/AlejandroFerp/EcoAdmin --skill branch-pr-alejandroferp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-pr
Source: https://github.com/AlejandroFerp/EcoAdmin/tree/main/.copilot/skills/branch-pr
Command: npx skills add https://github.com/AlejandroFerp/EcoAdmin --skill branch-pr-alejandroferp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically ensures PRs are linked to an approved issue and carry exactly one type:* label, preventing unreviewed or misclassified changes from entering codebase.

Core Features & Use Cases

  • Enforces issue linkage on PR creation and opening
  • Requires exactly one type:* label per PR
  • Validates branch names against the type/description pattern
  • Integrates with GitHub Actions to block merges until checks pass
  • Ideal for teams enforcing issue-first workflows and standardized PR hygiene

Quick Start

Create a new PR from a properly named branch to trigger the issue-linking and labeling checks.

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 on a GitHub pull request before merging?▼

To enforce issue linkage on a GitHub pull request, you can automate PR creation workflows that require an approved issue connection and exactly one type label before allowing a merge.

How do I validate git branch names against a type and description pattern?▼

Validating git branch names against a type and description pattern requires automated checks that ensure the branch naming convention matches your predefined workflow type before PR creation.

How do I require exactly one type label on a pull request in GitHub Actions?▼

Requiring exactly one type label on a pull request in GitHub Actions involves integrating automated checks that block merges until the single-type labeling rule is satisfied.

What is an issue-first workflow for pull requests and why use it?▼

An issue-first workflow for pull requests is a process enforcing that every PR links to an approved issue and carries a single type label, preventing unreviewed or misclassified changes from entering the codebase.

Can I use automated checks to block merges if a PR lacks an issue link?▼

Yes, you can use automated CI/CD integrations to block merges if a PR lacks an issue link, ensuring issue tracking enforcement and standardized PR hygiene are met before code changes merge.

What are the limitations of automating PR creation with branch-name validation?▼

Limitations of automating PR creation with branch-name validation include its strict reliance on CI/CD integrations and its unsuitability for teams not enforcing standardized issue-first workflows.

Related Skills

Explore More Software Engineering Skills→
lleontor705lleontor705
1

open-pr

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

Community
Advanced
mr-daedaliummr-daedalium
107

land-and-deploy

Merge PRs, trigger deployment, and verify canary health in CI/CD pipelines.

Community
Advanced
pulsemcppulsemcp

wait-for-ci

Block until GitHub Actions CI checks pass or fail on the current PR.

Official
Intermediate
etylsarinetylsarin
59

git-workflow

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

Community
Intermediate