gentle-ai-branch-pr

Validate pull requests against issue links and Conventional Commits conventions.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/LuisAlbertoMK/gentleman-agent-gh --skill gentle-ai-branch-pr-luisalbertomk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gentle-ai-branch-pr
Source: https://github.com/LuisAlbertoMK/gentleman-agent-gh/tree/main/skills/branch-pr
Command: npx skills add https://github.com/LuisAlbertoMK/gentleman-agent-gh --skill gentle-ai-branch-pr-luisalbertomk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates PR rejection by enforcing strict repository standards, ensuring every contribution is linked to an approved issue and meets quality requirements before submission.

Core Features & Use Cases

  • Issue-First Validation: Automatically verifies that PRs are linked to approved issues.
  • Quality Guardrails: Enforces a 400-line change limit and mandatory Conventional Commits formatting.
  • Use Case: Use this skill when you are ready to submit a feature or fix to the Gentle-AI repository to ensure your branch naming, commit messages, and PR body meet all CI requirements.

Quick Start

Use the gentle-ai-branch-pr skill to validate your current branch and generate a compliant pull request for the linked issue.

Frequently Asked Questions about gentle-ai-branch-pr

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

FAQPage Schema
How do I enforce issue-linked pull requests in my GitHub workflow?

Enforcing issue-linked pull requests requires automated validation that checks every PR against an approved issue before submission. This standardizes the PR lifecycle and prevents unlinked code from being merged into the repository.

What is issue-first validation for pull requests?

Issue-first validation is a workflow mechanism that verifies a pull request is linked to an approved issue before review. It enforces strict repository standards to ensure structural proof and bounded review within the development lifecycle.

Does this PR automation support Conventional Commits formatting and branch naming rules?

Yes, this PR automation supports Conventional Commits formatting and enforces repository-specific branch naming rules. It applies quality guardrails, including a 400-line change limit, to ensure contributions meet CI requirements.

How do I generate a compliant pull request for a linked GitHub issue?

To generate a compliant pull request, validate your current branch against repository standards and use automation to format the PR body with the linked issue reference. This ensures your submission meets all CI check requirements before review.

Why does my pull request fail CI checks when submitting a feature?

Your pull request may fail CI checks if it lacks an approved issue link, exceeds the 400-line change limit, or violates Conventional Commits formatting. Automated validation enforces these quality guardrails to prevent non-compliant submissions.

Can I use this workflow automation for large repository contributions?

This workflow automation is designed for standard feature and fix submissions but enforces a 400-line change limit per pull request. Contributions exceeding this limit must be split into smaller, bounded reviews to pass validation.