create-pr

Generate eight-section pull request bodies with ADR decision records.

4|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/greenheadHQ/nixos-config --skill create-pr-greenheadhq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/greenheadHQ/nixos-config/tree/main/modules/shared/programs/claude/files/skills/create-pr
Command: npx skills add https://github.com/greenheadHQ/nixos-config --skill create-pr-greenheadhq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Skill automates the creation of pull request bodies and manages updates to existing PRs by enforcing a structured eight-section template and ADR-driven decision records.

Core Features & Use Cases

  • Generates a complete PR body with sections: Summary, Existing Problem/Background, CIR (Change Intent Record), ADR (Architecture Decision Record), Implementation Details, References, Human Test Plan, and Pre-Merge E2E Test Guide.
  • Supports updating an existing PR body when given update arguments.
  • Includes ADR table generation to compare design options and capture trade-offs.
  • Leverages reference templates (pr-template.md, pre-merge-guide.md) to ensure documentation quality.

Quick Start

Ask to create PRs or update an existing PR to generate a complete eight-section PR body using the predefined templates.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I create a pull request with structured documentation and ADR?

To create a pull request with structured documentation, you generate a complete PR body using an eight-section template. This template automatically enforces sections for Architecture Decision Records, summaries, and implementation details to ensure documentation quality.

What is the best way to update an existing PR body with new decision records?

Updating an existing PR body with new decision records is done by passing update arguments to the PR automation process. This applies the structured eight-section template to the existing pull request, updating sections like the ADR and implementation details.

How does an ADR table help compare design options in a pull request?

An Architecture Decision Record (ADR) table in a pull request compares design options and captures trade-offs. It is generated as part of the structured PR template to document the rationale and decision context behind code changes.

What sections are needed for a complete pre-merge validation PR template?

A complete pre-merge validation PR template requires eight sections: Summary, Existing Problem/Background, Change Intent Record, ADR, Implementation Details, References, Human Test Plan, and Pre-Merge E2E Test Guide. These sections ensure frontmatter metadata and regression checks are met.

Can I automate pre-merge E2E test guidance within my pull request documentation?

Yes, you can automate pre-merge E2E test guidance within your pull request documentation. The PR generation process includes a dedicated Pre-Merge E2E Test Guide section by leveraging reference templates to ensure testing requirements are captured.