pr-formatting

Included with Lifetime

$97 forever

Create and update pull request descriptions with comprehensive, well-structured content. Use when the user asks to create a PR, mentions "pull request" or "PR", wants to merge a branch, or needs to update an existing PR description. Invokes /git-actions:pr-write (create draft PR) or /git-actions:pr-edit (update PR) commands which analyze commits, generate structured descriptions with testing/deployment notes, and handle approval workflow.

Writing & Docs

What this skill does

# Creating and Updating Pull Requests

When the user needs to create or update a pull request, use the appropriate slash command. These commands orchestrate the workflow with best practices built-in.

## Commands

### Create New PR
```bash
/git-actions:pr-write # Target main (or master if main doesn't exist)
/git-actions:pr-write develop # Target specific branch
/git-actions:pr-write main focus on security changes # With custom guidance
```

**What it does:**
1. Verifies not on base branch
2. Pushes branch to remote (if needed)
3. Analyzes all commits and changes
4. Generates comprehensive PR description
5. Presents for user approval
6. Creates **draft** PR on GitHub (requires gh CLI)

### Update Existing PR
```bash
/git-actions:pr-edit # Update current branch's PR
/git-actions:pr-edit 123 # Update specific PR by number
/git-actions:pr-edit 123 add performance metrics # With custom guidance
```

**What it does:**
1. Fetches current PR description
2. Analyzes commits and changes
3. Generates updated description
4. Presents for user approval
5. Updates PR on GitHub

## The pr-creator Agent

Both commands invoke the `pr-creator` agent, which has PR best practices embedded:
- Checks for repository PR template first (follows if exists)
- Generates clear, scannable structure
- Includes: Summary, Changes, Testing, Deployment Notes
- Organizes changes by component/area, not by file
- Provides comprehensive testing checklist
- Adapts to repository style

## Custom Instructions

You can pass additional context to customize the output:

```bash
/git-actions:pr-write brief format
/git-actions:pr-edit 123 emphasize breaking changes
/git-actions:pr-write main focus on performance improvements
```

## Draft Mode

All PRs are created in **draft mode** for review before publishing:
- Review the generated description
- Edit if needed: `/git-actions:pr-edit`
- Mark ready when satisfied: `gh pr ready`

## Examples

**User:** "I'm done with this feature, create a PR"
**You:** Use `/git-actions:pr-write` to create a draft PR with a comprehensive description.

**User:** "Create a PR to develop branch"
**You:** Use `/git-actions:pr-write develop` to target the develop branch instead of main.

**User:** "Update the PR description with the new changes"
**You:** Use `/git-actions:pr-edit` to regenerate the PR description based on current commits.

**User:** "The PR needs more emphasis on the security fixes"
**You:** Use `/git-actions:pr-edit focus on security changes` to update the description with security emphasis.

Files: 1

Size: 3.0 KB

Complexity: 15/100

Category: Writing & Docs

Source: https://github.com/olioapps/claude-code-plugins/tree/main/git-actions/skills/pr-formatting

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts