coding-bro-ai-branch-pr

Enforce issue-linked, labeled GitHub PRs with five automated check gates.

Updated Apr 1, 2026

Search Tags:#git #workflow #github #branch #pr #labels #pull-request

Ready to run

npx skills add https://github.com/maxculen86/coding-bro-ai --skill coding-bro-ai-branch-pr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coding-bro-ai-branch-pr
Source: https://github.com/maxculen86/coding-bro-ai/tree/main/skills/branch-pr
Command: npx skills add https://github.com/maxculen86/coding-bro-ai --skill coding-bro-ai-branch-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR creation workflow for Gentle AI following the issue-first enforcement system. This skill enforces a disciplined PR workflow that guarantees every PR links an approved issue, carries exactly one type label, and passes a defined set of automated checks.

Core Features & Use Cases

Linkage enforcement: PR bodies must reference an approved issue with Closes/Fixes/Resolves #<N>.
Label discipline: apply exactly ONE type label to the PR.
Quality gates: ensure all five automated checks pass before merge.
Use Case: when preparing fixes or features, follow the branch naming conventions and PR template to maintain governance.

Quick Start

Load this skill when you are preparing a PR: create a branch following the naming pattern, apply exactly one type label, reference the issue in the PR body, and ensure all checks pass.

Frequently Asked Questions about coding-bro-ai-branch-pr

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

FAQPage Schema

How do I enforce issue linking in GitHub pull requests?▼

GitHub pull request enforcement requires PR bodies to reference an approved issue using Closes, Fixes, or Resolves with the issue number. This governance guarantees every PR links an approved issue before proceeding through automated checks.

What's the best way to automate PR labeling and branch naming for GitHub workflows?▼

Automating PR labeling and branch naming involves enforcing strict conventions: branches must follow defined naming patterns for features or fixes, and PRs must carry exactly one type label to maintain workflow discipline.

How do I set up quality gates for a GitHub pull request?▼

Setting up PR quality gates requires defining a set of automated checks that must pass before merge. This workflow enforces five automated checks alongside issue linkage and label discipline to prepare changes for review.

Can I use this PR workflow governance for both feature and fix branches?▼

Yes, this PR workflow governance applies to creating both feature and fix branches. It ensures adherence to branch naming patterns and PR templates, maintaining consistent issue-first discipline across all repository changes.

Why does my GitHub pull request fail automated checks before merge?▼

GitHub pull requests fail automated checks when governance rules are violated, such as missing issue references in the PR body, multiple or missing type labels, or failing any of the five defined automated quality checks before merge.