make-pr

Creates GitHub pull requests to main with a validated five-section PT-BR description template.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/quanthubbr/tron-claude-config --skill make-pr-quanthubbr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: make-pr
Source: https://github.com/quanthubbr/tron-claude-config/tree/main/managed/skills/make-pr
Command: npx skills add https://github.com/quanthubbr/tron-claude-config --skill make-pr-quanthubbr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Opening a pull request often means writing a vague or inconsistent description, forgetting required sections, or bypassing team conventions. This Skill enforces a canonical PT-BR PR template with five mandatory sections, validates the body before creation, and produces a concise, reviewer-friendly pull request via the GitHub CLI. ## Core Features & Use Cases - Enforced PT-BR Template: Generates PR bodies with exactly five mandatory sections (Resumo, Principais mudanças, Arquitetura & implementação, Antes → Agora, Roteiro de teste), blocking English headers. - Pre-Creation Validation: Writes the draft to .claude/.pr-body-draft.md and validates it with validate-pr-body.cjs before running gh pr create, retrying until it passes. - Context-Grounded Descriptions: Inspects git log and git diff against main so the description reflects actual changes rather than guesses. - Use Case: After finishing a feature branch and committing with /commit-changes, invoke this Skill to open a PR to main with a complete, validated Portuguese description readable in under five minutes. ## Quick Start Ask the assistant to open a pull request to main for the current feature branch using the make-pr skill.

Frequently Asked Questions about make-pr

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

FAQPage Schema
How do I create a pull request with the GitHub CLI from a feature branch?▼

Run gh pr create with --base main, --head set to your branch, a semantic title, and --body-file pointing to a validated draft file. This Skill writes the draft to .claude/.pr-body-draft.md and validates it before creating the PR.

How to write a pull request description that passes template validation?▼

Include exactly five PT-BR headers in order: Resumo, Principais mudanças, Arquitetura & implementação, Antes → Agora, and Roteiro de teste. English headers like Summary or Test plan are blocked by the validation hook.

Can I use English section headers like Summary in the PR body?▼

No. The hook blocks English headers such as Summary, Test plan, or Changes. All five sections must use the PT-BR titles, and non-applicable sections must include the header with a N/A placeholder line.

Why does gh pr create fail with a template validation error?▼

The hook validates the actual gh pr create command and requires --body-file .claude/.pr-body-draft.md containing all five PT-BR headers. Inline --body, --editor, or --fill flags are blocked, so fix the draft and re-run validation.

What must be done before opening a pull request with this workflow?▼

The current branch must be a feature branch pushed and up to date with origin, with no uncommitted changes. If changes are pending, run /commit-changes first, and ensure the gh CLI is authenticated.