gentle-ai-collab-perfect

Enforce issue-first workflows and PR body standards for external contributions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the friction and high rejection rate faced by external contributors when interacting with the Gentleman-Programming/gentle-ai repository by enforcing strict adherence to the project's unique issue-first and receipt-driven development policies.

Core Features & Use Cases

  • Workflow Enforcement: Validates PRs against the mandatory issue-first policy, ensuring every change is linked to an approved issue.
  • API-Driven Verification: Cross-references PR metadata, labels, and test results against the GitHub API to prevent common 403 errors and policy violations.
  • Strategy Guidance: Provides expert advice on choosing between Stacked PRs and Feature Branch Chains based on repository constraints.

Quick Start

Use the gentle-ai-collab-perfect skill to audit my current pull request against the repository contribution guidelines and identify any missing maintainer-required actions.

Frequently Asked Questions about gentle-ai-collab-perfect

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

FAQPage Schema
How do I ensure my pull request passes automated CI gates for external contributions?

To ensure your pull request passes automated CI gates, you must follow an issue-first workflow and meet strict PR body standards. This validates your PR metadata against the GitHub API to prevent policy violations and common 403 errors.

What is the issue-first workflow for GitHub pull requests?

The issue-first workflow requires linking every code change to an approved issue before submission. It governs the entire contribution lifecycle from initial issue creation and branch naming to final pull request auditing and verification.

How do I choose between stacked PRs and feature branch chains for my contribution?

Choosing between stacked PRs and feature branch chains depends on specific repository constraints. Expert strategy guidance evaluates your pull request scope and API-verified contributor boundaries to recommend the correct branching approach.

Why does my GitHub pull request fail contributor scope verification?

Your pull request fails contributor scope verification when metadata, labels, or test results do not match GitHub API requirements. Cross-referencing these elements against API data enforces strict contributor-vs-maintainer boundaries and prevents policy violations.

Do I need conventional commit formatting for automated pull request audits?

Yes, conventional commit formatting is a mandatory technical requirement for automated CI gates. The auditing process verifies that your commits and pull request body satisfy all formatting standards before integration.