skills.rest
kurojs
kurojsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

branch-pr

Validate pull requests for approved issue references, type labels, and branch naming.

2|Updated Jul 29, 2025
Search Tags:#code review#pull request#github#shellcheck#branch naming#labels#issue linkage
One-click install
npx skills add https://github.com/kurojs/EnderDots --skill branch-pr-kurojs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-pr
Source: https://github.com/kurojs/EnderDots/tree/main/.config/opencode/skills/branch-pr
Command: npx skills add https://github.com/kurojs/EnderDots --skill branch-pr-kurojs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents slow, error-prone pull requests by enforcing issue-first references and consistent PR metadata before code changes are reviewed.

Core Features & Use Cases

  • Issue-first PR enforcement: Blocks PRs unless they explicitly close, fix, or resolve an approved issue.
  • Single, consistent PR type: Requires exactly one type:* label so triage and automation stay reliable.
  • Branch + PR correctness checks: Guides you to create branches using a strict type/description pattern and to run required automated validations (including shellcheck) prior to review.

Quick Start

Ask your AI agent to create a PR using the provided approved issue number, set the PR body to include a single valid issue-closing line, add exactly one type:* label, and ensure automated checks pass after running shellcheck on any modified shell scripts.

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 creating a GitHub pull request?▼

To enforce issue linkage for a GitHub pull request, you must reference an approved issue number in the PR body using a closing keyword like 'closes', 'fixes', or 'resolves' to ensure predictable review and automation.

What is the correct branch naming pattern for a review-ready pull request?▼

The correct branch naming pattern for a review-ready pull request follows a strict type/description format, matching conventional commit changes like feature, fix, chore, or docs to maintain consistency across the repository.

Why does my pull request fail validation if I add multiple type labels?▼

Your pull request fails validation with multiple type labels because the workflow enforces exactly one type:* label per PR, ensuring that automated triage and downstream automation processes remain reliable and predictable.

Do I need to run shellcheck before opening a pull request?▼

Yes, you need to run shellcheck on any modified shell scripts before opening a pull request, as the workflow requires automated checks to pass to ensure your changes are review-ready and meet validation guardrails.

Can I open a pull request without an approved issue reference?▼

No, you cannot open a pull request without an approved issue reference, as the issue-first enforcement blocks PR creation unless they explicitly close, fix, or resolve an approved issue to prevent slow and error-prone reviews.

Related Skills

Explore More Software Engineering Skills→
gendosugendosu

pull-request

Create or update a pull request for the current branch with issue reference.

Community
Intermediate
AlejandroFerpAlejandroFerp

branch-pr

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

Community
Intermediate
aaddrickaaddrick
5.3k

lint

Lint shell scripts with shellcheck and GitHub Actions workflows with actionlint.

Community
Basic
zMynxxzMynxx

branch-pr

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

Community
Intermediate