pr

Generate a GitHub pull request title and body from the current branch.

3|1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/ncaq/konoka --skill pr-ncaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/ncaq/konoka/tree/main/plugins/pr/skills/pr
Command: npx skills add https://github.com/ncaq/konoka --skill pr-ncaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a GitHub pull request title and body from the current branch, and prompt you to review before you create it. This skill streamlines PR creation by drafting content automatically and guiding you through validation. It handles only new pull requests; updating existing PRs is out of scope.

Core Features & Use Cases

  • Auto-generate PR title and body from the current branch following repository conventions.
  • Synchronize with the base branch (including optional rebasing) to keep history clean before PR creation.
  • Prompt for user confirmation, and support downstream steps for assigning the PR and applying labels after creation.

Quick Start

Create a new pull request from your current branch by following the guided workflow and confirming the generated title, body, assignees, and labels.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I generate a GitHub pull request title and body from my current branch?

To generate a GitHub pull request from your current branch, this skill drafts the title and body automatically following repository conventions. It then prompts you to review and confirm the content before creation, ensuring accuracy.

Can I assign reviewers and apply labels automatically when creating a pull request?

Yes, you can assign reviewers and apply labels when creating a pull request. After generating the PR content and confirming creation, the workflow supports downstream steps to assign the PR and apply relevant labels.

Does the pull request workflow synchronize with the base branch before creating the PR?

The pull request workflow synchronizes with the base branch before creation. It coordinates base synchronization and supports optional rebasing to keep your commit history clean prior to opening the pull request.

What is the best way to streamline pull request creation while keeping commit history clean?

The best way to streamline pull request creation while keeping history clean is to auto-generate the PR content, synchronize with the base branch via optional rebasing, and prompt for user approval before submission.

Can I update an existing pull request using this automated workflow?

No, you cannot update an existing pull request with this workflow. The skill handles only new pull request creation; updating existing PRs is explicitly out of scope.

Do I need user approval before the pull request is actually created on GitHub?

Yes, you need user approval before the pull request is created on GitHub. The workflow ensures PR creation proceeds only after you review and explicitly approve the generated title, body, and metadata.