skills.rest
zMynxx
zMynxxCOMMUNITY
Explore all skills by this author →
GitHub

branch-pr

Validate GitHub pull requests for issue linkage, branch naming, and commit conventions.

Updated Jun 5, 2026
Search Tags:#code review#pull request#conventional commits#github#issue tracking#branch
One-click install
npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill branch-pr-zmynxx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-pr
Source: https://github.com/zMynxx/bifrost-with-opencode/tree/main/.opencode/skills/branch-pr
Command: npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill branch-pr-zmynxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inconsistent pull request workflows by enforcing issue linkage, branch conventions, commit standards, labels, and validation requirements before code review.

Core Features & Use Cases

  • Issue-First PR Workflow: Ensures pull requests are connected to approved issues and meet repository contribution rules.
  • Branch and Commit Validation: Guides contributors through compliant branch naming and conventional commit formats.
  • PR Preparation Support: Helps developers create review-ready pull requests with required templates, labels, checklists, and automated checks.

Quick Start

Use the branch-pr skill to prepare my current changes for a compliant GitHub pull request.

Frequently Asked Questions about branch-pr

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

FAQPage Schema
How do I ensure my pull request is linked to an approved GitHub issue?▼

Validating issue linkage for pull requests requires connecting your branch to an approved GitHub issue. This Skill enforces an issue-first workflow that verifies the connection before code review submission.

What is the correct way to format conventional commits for a compliant pull request?▼

Formatting conventional commits for a compliant pull request requires adherence to specific commit message standards. This Skill guides contributors through validating commit conventions to ensure repository-specific formatting rules are met before review.

How do I prepare a GitHub branch for code review submission?▼

Preparing a GitHub branch for code review submission involves validating branch naming conventions, commit standards, and required PR templates. This Skill coordinates these checks to help developers create review-ready pull requests with necessary labels and automated checks.

Does this enforce repository-specific PR templates and labels?▼

Yes, this enforces repository-specific PR templates and labels. It validates that your pull request meets the required automated checks, checklists, and contribution rules defined by the repository before submitting for code review.

Why does my pull request workflow fail branch naming validation?▼

Pull request workflows fail branch naming validation when branch conventions do not adhere to repository-specific standards. This Skill prevents inconsistent workflows by guiding contributors through compliant branch naming formats before opening pull requests.

Related Skills

Explore More Software Engineering Skills→
toqoztoqoz

commit-staged

Commit staged git changes with Conventional Commits and branch protection.

Community
Advanced
yanochka11yanochka11

iterate-pr

Iterate pull requests by resolving CI failures and review feedback until validation succeeds.

Community
Advanced
BrunoAMSilvaBrunoAMSilva

git-commit

Generate Conventional Commits messages from repository diffs and stage files.

Community
Intermediate
RyoMurakami1983RyoMurakami1983
2

git-initial-setup

Automates GitLab project and repository setup for streamlined onboarding and management.

Community
Intermediate