pull-request-creator

Create standardized pull requests with branch names, titles, and templated descriptions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/freddomingues/think-tars --skill pull-request-creator-freddomingues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull-request-creator
Source: https://github.com/freddomingues/think-tars/tree/main/.cursor/skills/pull-request-creator
Command: npx skills add https://github.com/freddomingues/think-tars --skill pull-request-creator-freddomingues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes the process of opening pull requests for the think-tars repository, ensuring clear, consistent descriptions and adherence to workflow conventions.

Core Features & Use Cases

  • PR description template: Provides a structured body outlining changes, rationale, and validation steps.
  • Branch and title conventions: Enforces kebab-case branch names and concise, informative PR titles.
  • Trigger-aware prompts: Responds to signals like "criar PR", "pull request", "abrir PR", "descrição da PR", "explicar o que foi feito", "preparar PR", "merge request" to generate ready-to-open PR content.

Quick Start

Invoke the skill to generate a PR draft for a new feature, including branch name, title, and a templated description, then open the PR on GitHub using the generated content.

Frequently Asked Questions about pull-request-creator

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

FAQPage Schema
How do I create a standardized pull request template for GitHub?

A standardized pull request template provides a structured body outlining changes, rationale, and validation steps. It enforces kebab-case branch names and concise, informative PR titles to guide reviewers and merge decisions.

What is the best way to generate a PR description with clear branch naming conventions?

Generating a PR description with clear branch naming conventions involves enforcing kebab-case for branch names alongside templated explanations of changes. This ensures predictable PR workflows and consistent descriptions for code review.

How do I automate pull request creation with trigger-based activation?

Automating pull request creation with trigger-based activation responds to signals like 'criar PR', 'pull request', or 'abrir PR' to generate ready-to-open PR content. It produces a draft including the branch name, title, and templated description.

Can I use a templated PR description to guide reviewers through code changes?

Yes, you can use a templated PR description to guide reviewers through code changes. The template provides a structured body that outlines changes, rationale, and validation steps to support merge decisions.

What should I include in a pull request description for consistent code review?

A pull request description for consistent code review should include a structured body outlining changes, rationale, and validation steps. It also requires a concise, informative PR title and a kebab-case branch name to maintain workflow conventions.

Does this PR creation tool work without external dependencies?

Yes, this PR creation tool works without external dependencies. It operates independently to enforce a canonical template and trigger-based activation for generating standardized pull request content on GitHub.