pull-request

Generates GitHub pull request titles and bodies following repository conventions.

Updated Feb 24, 2025
One-click install
npx skills add https://github.com/maarten00/dotfiles --skill pull-request-maarten00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/maarten00/dotfiles/tree/main/skills/pull-request
Command: npx skills add https://github.com/maarten00/dotfiles --skill pull-request-maarten00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent pull request titles and bodies is repetitive and error-prone: titles must be changelog-ready English one-liners, bodies must follow the repo's PR template in Dutch, and exactly one label must be applied. This Skill encodes all of those rules so every PR you open matches the team's conventions automatically. ## Core Features & Use Cases - Changelog-ready titles: Writes short, imperative English titles from the end-user's perspective, optionally appending a Notion ticket tag like [EXO-1234]. - Template-compliant Dutch bodies: Fills the repo's PR template (What does it do? / How to test? / Issues) in Dutch developer-speak, with concrete frontend click-paths or API call examples for testers. - Label and compliance handling: Applies exactly one appropriate label via gh CLI and appends the mandatory AI-generated disclaimer to every PR body. - Use Case: After finishing a bugfix branch, ask the assistant to open a PR — it drafts the title, writes the Dutch body with test steps, applies the bugfix label, and creates the PR with gh pr create. ## Quick Start Ask the assistant to open a pull request for the current branch using the pull-request rules, including the title, Dutch body, and one label.

Frequently Asked Questions about pull-request

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

FAQPage Schema
How do I write a good GitHub pull request title?▼

Write a short, imperative English title that reads as a one-line release note, describing the change from the end-user's perspective. Append the issue tag like [EXO-1234] when a ticket exists, and match the style of existing titles in the repo.

How to create a pull request with gh CLI following a template?▼

Use gh pr create with a body that follows the repo's .github/PULL_REQUEST_TEMPLATE.md sections: What does it do, How to test, and Issues. This Skill drafts that body in Dutch and can attach one label via the --label flag.

Can I include a Notion ticket in my pull request?▼

Yes, providing a Notion link is optional. When Notion access is available, the EXO-XXXX ticket number is read from the page and appended to the PR title and Issues section; otherwise the PR proceeds without it.

What should the How to test section of a PR contain?▼

Describe how another developer verifies the change: preferably a concrete click-path in the admin or portal frontend, or API calls with method, endpoint, JSON body, and expected response. Never write 'run unit test X' as a test instruction.

How many labels should a pull request have?▼

Apply exactly one label yourself, choosing the type that best captures the change, such as bugfix, new-feature, or enhancement. Labels added automatically by the repo are separate and should be left in place.