wtf.create-pr

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

7|2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/xiduzo/wtf --skill wtf-create-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wtf.create-pr
Source: https://github.com/xiduzo/wtf/tree/main/skills/wtf.create-pr
Command: npx skills add https://github.com/xiduzo/wtf --skill wtf-create-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open context-aware PRs for completed task branches by reading the Task + Feature + Epic hierarchy to craft meaningful PR descriptions and handle branches with or without a linked task issue.

Core Features & Use Cases

  • Reads the full spec hierarchy (Task → Feature → Epic) to craft a PR description that clearly communicates intent.
  • Determines the correct base branch (task/* → parent feature; feature/* → main) and generates a PR body that explains why the change was necessary.
  • Supports PR lifecycle actions such as detecting existing PRs, updating descriptions, and preparing reviewer assignments based on repository conventions.

Quick Start

Open the task branch and run the create-pr workflow to generate a PR draft and description automatically.

Frequently Asked Questions about wtf.create-pr

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

FAQPage Schema
How do I create a pull request with context from a task branch?▼

To create a pull request with task branch context, the workflow identifies your current branch, extracts linked Task, Feature, or Epic metadata, and generates a context-aware PR title and body explaining why the changes were made.

How does PR generation work when a feature branch is linked to an Epic hierarchy?▼

PR generation works by reading the full spec hierarchy from Task to Feature to Epic, consulting the branch diff, and crafting a meaningful PR description that clearly communicates the intent behind the changes.

Can I update an existing PR description instead of creating a new one?▼

Yes, you can update an existing PR description. The workflow detects whether a PR already exists for the current branch and prepares actions to update the description or handle the existing PR lifecycle accordingly.

How do I target the correct base branch when opening a PR from a task branch?▼

To target the correct base branch, the workflow automatically determines the appropriate parent branch by routing task branches to their parent feature branch, and feature branches directly to main.

Do I need a linked task issue to generate a pull request?▼

You do not need a linked task issue to generate a pull request. The workflow handles branches with or without a linked task issue by extracting available repository metadata to craft the PR body.

What is the best way to prepare a PR draft for reviewer assignment?▼

The best way to prepare a PR draft for reviewer assignment is to run the create-pr workflow, which generates a draft for review and prepares optional steps like adding reviewers and commenting on linked tasks based on repository conventions.