skills.rest
LuisAlbertoMK
LuisAlbertoMKCOMMUNITY
Explore all skills by this author →
GitHub

branch-pr

Validates Git branches and commits for repository compliance before submission using Shellcheck and the GitHub CLI.

Updated Apr 28, 2026
Search Tags:#automation#git#workflow#github#compliance#pull-request
One-click install
npx skills add https://github.com/LuisAlbertoMK/gentleman-agent-gh --skill branch-pr-luisalbertomk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-pr
Source: https://github.com/LuisAlbertoMK/gentleman-agent-gh/tree/main/internal/assets/skills/branch-pr
Command: npx skills add https://github.com/LuisAlbertoMK/gentleman-agent-gh --skill branch-pr-luisalbertomk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates manual PR errors and compliance gaps by enforcing strict issue-linkage, conventional commit standards, and automated validation checks before submission.

Core Features & Use Cases

  • Issue-First Validation: Ensures every pull request is tied to an approved issue, preventing orphaned code changes.
  • Automated Compliance: Enforces branch naming conventions, conventional commit formats, and mandatory label application.
  • Use Case: When preparing a new feature, use this skill to automatically verify that your branch name, commit history, and PR body meet the repository's quality standards before opening the request.

Quick Start

Execute the branch-pr skill to validate your current branch configuration and generate a compliant pull request template linked to your approved issue.

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

To enforce issue linkage for a GitHub pull request, you can automate validation checks that verify every PR is tied to an approved issue, preventing orphaned code changes before submission.

Can I automate branch naming convention checks for my CI/CD workflow?▼

Yes, you can automate branch naming convention checks within a CI/CD workflow by running pre-submission verification scripts that validate repository governance rules before generating PR metadata.

What is conventional commit formatting validation for pull requests?▼

Conventional commit formatting validation for pull requests is an automated compliance check that ensures commit histories meet standardized repository quality standards before the code changes are submitted.

Do I need GitHub CLI and Shellcheck to automate PR compliance checks?▼

Yes, you need GitHub CLI and Shellcheck installed in your environment to perform pre-submission verification and generate compliant PR metadata for automated pull request compliance checks.

Why do my pull requests fail repository governance compliance checks?▼

Pull requests fail repository governance compliance checks when they lack strict issue linkage, have improper branch naming, or fail to meet conventional commit standards during automated validation.

What's the best way to standardize pull request workflows with issue-first checks?▼

The best way to standardize pull request workflows with issue-first checks is to apply automated validation that verifies branch naming, commit formats, and mandatory labels before opening the request.

Related Skills

Explore More Software Engineering Skills→
Sumeet138Sumeet138
1

shellcheck-configuration

Install ShellCheck and configure linting rules via .shellcheckrc.

Community
Intermediate
krzysztofsurdykrzysztofsurdy
20

cicd

Design CI/CD pipelines with deployment strategies and environment management.

Community
Advanced
brivarobrivaro

github-pr

Create GitHub Pull Requests with conventional commits via the GitHub CLI.

Community
Intermediate
CodenburgCodenburg

branch-pr

Validate pull requests against approved issues and branch naming conventions.

Community
Intermediate