pr-writer

Name: pr-writer
Availability: InStock
Author: Promptly

Enforce PR title and description formats with Jira linking via GitHub CLI.

Updated Aug 23, 2026

Search Tags:#workflow #conventions #jira #pr #code-review #pull-request

Ready to run

npx skills add https://github.com/promptlylabs/skills --skill pr-writer-promptlylabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-writer
Source: https://github.com/promptlylabs/skills/tree/main/plugins/promptly-skills/skills/pr-writer
Command: npx skills add https://github.com/promptlylabs/skills --skill pr-writer-promptlylabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures pull requests are created and updated according to Promptly Health conventions, reducing review back-and-forth and misaligned metadata by enforcing standardized titles, descriptions, and Jira linking.

Core Features & Use Cases

Enforces PR title and body structure per the project conventions.
Automatically detects and links Jira tickets from the branch name into the PR.
Provides a ready-to-use PR description template and drafting workflow for consistent reviews.
Supports draft PR workflows and updates to PR metadata via GitHub API when needed.

Quick Start

Generate a draft PR title and description that follow the project conventions and embed the Jira ticket reference.

Frequently Asked Questions about pr-writer

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

FAQPage Schema

How do I standardize pull request titles and descriptions for consistent code review?▼

Standardize pull request titles and descriptions by enforcing PR format conventions and applying structured templates, which reduces review back-and-forth and misaligned metadata. The Skill validates title and body structure against project conventions before a PR is drafted or updated.

How do I automatically link Jira tickets to a pull request from the branch name?▼

Automatically link Jira tickets to a pull request by detecting the ticket reference directly from the branch name. The Skill extracts the Jira identifier during PR creation and embeds it into the PR metadata to maintain traceability across plan-driven changes.

Do I need GitHub CLI or API access to draft and update PRs with enforced conventions?▼

Yes, you need GitHub CLI or API access to draft, update, and link Jira tickets for pull requests with enforced conventions. This access is required to apply structural checks, manage draft PR workflows, and prevent non-conforming PRs from being merged.

What's the best way to generate a draft PR description that follows project conventions?▼

The best way to generate a draft PR description is using a ready-to-use template workflow that enforces project conventions. This standardizes the PR creation process by applying consistent title and body structures, ensuring reviews start with aligned metadata.

Can I update PR metadata via the GitHub API when branch changes are plan-driven?▼

Yes, you can update PR metadata via the GitHub API when managing plan-driven branch changes. The Skill supports updating PR titles and descriptions to maintain compliance with conventions as the branch evolves, preventing non-conforming PRs from slipping through.

Why does my pull request get blocked for not following code review conventions?▼

A pull request gets blocked for not following code review conventions because automated checks validate the PR title, body structure, and Jira linking. This enforcement prevents non-conforming PRs from bypassing the standardized review workflow required by the project.