ce-pr-description

Generate conventional-commit PR titles and bodies for gh pr workflows.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/yxc023/agent-config-studio --skill ce-pr-description-yxc023
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-pr-description
Source: https://github.com/yxc023/agent-config-studio/tree/main/.opencode/skills/ce-pr-description
Command: npx skills add https://github.com/yxc023/agent-config-studio --skill ce-pr-description-yxc023

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill generates a conventional-commit-style PR title and a value-first body describing the work of a pull request, reducing manual writing and ensuring consistency across PRs.

Core Features & Use Cases

  • Generate a PR title and detailed body from a natural-language prompt or a specified PR reference.
  • Support current-branch mode (describe HEAD vs base) or PR mode (URL, pr:, #NN, or bare number) with optional steering text.
  • Return a structured {title, body_file} for downstream gh pr edit or gh pr create workflows, with the body written to an OS temp file and no direct mutation performed.

Quick Start

Describe this branch's changes as a PR description.

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 PR description from a branch diff automatically?

To generate a PR description automatically, this skill analyzes your branch changes and produces a conventional-commit-style title with a value-first body, returning a structured output for downstream workflows.

What is the best way to write a conventional-commit-style pull request title?

The best way to write a conventional-commit-style pull request title is to use this skill, which evaluates your code changes or a specified PR reference and generates a standardized, value-first title and body.

Can I generate GitHub pull request text using a PR number or URL?

Yes, you can generate GitHub pull request text by providing a URL, pr: prefix, #NN, or a bare number as input, allowing the skill to operate in PR mode and describe the referenced pull request.

Does the PR generation skill directly edit or mutate my existing pull request?

No, the PR generation skill does not mutate your existing pull request; it writes the generated body to an OS temp file and returns a structured object for you to use with downstream gh commands.

How to create a PR body file for downstream gh pr edit commands?

To create a PR body file for downstream gh pr commands, this skill writes the generated pull request body to an OS temp file and returns the file path alongside the title without directly mutating the PR.

Can I add steering text to guide the pull request description generation?

Yes, you can add optional steering text alongside your current branch or PR reference input to guide the pull request description generation, ensuring the output reflects specific contextual priorities.