skills.rest
thisisryanswift
thisisryanswiftCOMMUNITY
Explore all skills by this author →
𝕏@thisisrsyanswiftGitHub

ce-pr-description

Generate a conventional-commit-style PR title and value-first body file.

2|Updated Apr 30, 2026
Search Tags:#automation#workflow#diff#pr#description#pull-request#title
One-click install
npx skills add https://github.com/thisisryanswift/zellij-agent-tools --skill ce-pr-description-thisisryanswift
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-pr-description
Source: https://github.com/thisisryanswift/zellij-agent-tools/tree/main/.opencode/skills/ce-pr-description
Command: npx skills add https://github.com/thisisryanswift/zellij-agent-tools --skill ce-pr-description-thisisryanswift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a conventional-commit-style PR title and a value-first body for a PR described by a URL/number or for the current HEAD against its base, enabling consistent PR narratives without manual drafting.

Core Features & Use Cases

  • Generate a conventional-commit-style title and a value-first body for a PR described by a URL/number or for the current HEAD against its base.
  • Return a structured {title, body_file} for downstream use by gh pr edit or gh pr create, without applying changes itself.
  • Support current-branch mode (HEAD vs base) and PR mode (accepts full URL, pr:, #NN, or bare number) and prepare the narrative for integration into PR workflows.

Quick Start

Describe the current branch or a specified PR to generate a title and a body file for a PR.

Frequently Asked Questions about ce-pr-description

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

FAQPage Schema
How do I generate a pull request description from a git diff automatically?▼

This skill generates a pull request description from a git diff by analyzing the current branch against its base, producing a conventional-commit-style title and a value-first body for your PR workflow.

What is a conventional-commit-style PR title and how does it structure pull request changes?▼

A conventional-commit-style PR title uses standardized prefixes to categorize changes, while a value-first body explains the impact of the diff, ensuring consistent and clear pull request narratives without manual drafting.

Can I use a PR number or URL to generate a description for an existing pull request?▼

Yes, PR mode accepts a full URL, pr:, #NN, or a bare number to generate a title and body file for an existing pull request, returning structured output without modifying the PR itself.

How do I create a PR with gh pr create using an automated description body file?▼

The skill writes the generated PR body to an OS temp file and returns a structured {title, body_file} output, which you can pass directly as arguments to downstream gh pr create or gh pr edit commands.

Does the PR description generator modify my existing pull request directly?▼

No, the PR description generator does not modify your existing pull request directly; it only returns the title and a body file path for the caller to apply via gh CLI commands.

Related Skills

Explore More Software Engineering Skills→
xiduzoxiduzo
7

wtf.create-pr

Generate pull request titles and descriptions from branch names and spec hierarchies.

Community
Advanced
Andreicr1Andreicr1

ce-pr-description

Generate conventional-commit PR titles and descriptive bodies for branches or PRs.

Community
Advanced
JacksonZx535JacksonZx535

ship

Automate software release workflows with Git and GitHub PR creation.

Community
Advanced
ulises-jeremiasulises-jeremias
2

dots-workstation-pr-fallback

Generate structured pull request bodies with YAML and Markdown placeholders.

Community
Intermediate