pr-formation

Standardize pull request titles and descriptions using project-specific templates.

3|2|Updated May 12, 2026

Search Tags:#automation #documentation #github #communication #code-review #pull-request

Ready to run

npx skills add https://github.com/kriscendobot/garden --skill pr-formation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-formation
Source: https://github.com/kriscendobot/garden/tree/main/skills/pr-formation
Command: npx skills add https://github.com/kriscendobot/garden --skill pr-formation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of poorly structured pull request descriptions that force maintainers to hunt for intent, context, and scope, leading to unnecessary review cycles.

Core Features & Use Cases

Standardized PR Templates: Enforces the use of upstream templates to ensure consistency across all contributions.
Intent-Focused Writing: Guides the agent to prioritize behavior and intent over file-level diff details, improving readability.
Use Case: When a gardening job completes a feature, this skill ensures the resulting PR clearly explains the what, why, and scope of the change, preventing methodology leaks and keeping the focus on the maintainer's needs.

Quick Start

Use the pr-formation skill to draft a pull request description that follows the upstream template and focuses on the behavioral impact of the changes.

Frequently Asked Questions about pr-formation

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

FAQPage Schema

How do I write a pull request description that maintainers can review quickly?▼

Standardize your pull request descriptions by focusing on behavior and intent rather than file-level diffs. Applying project-specific templates ensures the PR prose clearly communicates the what, why, and scope, which reduces unnecessary review cycles.

What should a GitHub pull request body include after scope changes?▼

After scope changes, a GitHub pull request body should be rewritten to reflect the updated behavioral impact and exclude internal methodology. Adhering to the upstream template during rewrites ensures the description remains maintainer-ready and intent-focused.

Does automated PR documentation need to include file-level diff callouts?▼

No, automated PR documentation should exclude file-level diff callouts and internal methodology. Focusing on behavioral impact and intent rather than specific file changes improves readability and keeps the description aligned with maintainer needs.

Can I use project-specific templates for pull request creation and body rewrites?▼

Yes, you can and should use project-specific templates for both initial pull request creation and subsequent body rewrites. Enforcing upstream templates guarantees consistency across all contributions and standardizes the communication of scope changes.

Why does my pull request title need to follow an upstream template?▼

Your pull request title needs to follow an upstream template to solve the problem of poorly structured contributions. Standardized titles enforce consistency, preventing maintainers from hunting for intent and context, which directly improves overall review efficiency.

What is the best way to automate communication in a code review pull request?▼

The best way to automate code review communication is to standardize PR prose generation around behavioral impact. This approach prevents methodology leaks and prioritizes the maintainer's need for clear context over granular file-level changes.