feature-branch-pr-writing

Draft conventional-commit PR titles and descriptions for feature-branch pull requests.

41|5|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/shopwareLabs/ai-coding-tools --skill feature-branch-pr-writing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-branch-pr-writing
Source: https://github.com/shopwareLabs/ai-coding-tools/tree/main/plugins/contributor-writing/skills/feature-branch-pr-writing
Command: npx skills add https://github.com/shopwareLabs/ai-coding-tools --skill feature-branch-pr-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft PR titles and descriptions for non-trunk feature-branch pull requests to ensure consistency, clarity, and efficient review by summarizing the branch's intent and changes.

Core Features & Use Cases

  • Drafts conventional-commit-style PR titles for changes that touch multiple areas.
  • Generates narrative PR descriptions with sections covering rationale, diffs, and related PRs.
  • Guides questioning for missing context by referencing linked PRs and branch state.
  • Useful for teams adopting standardized PR conventions and rapid review.

Quick Start

Ask Claude Code to draft a feature-branch PR title and narrative description for the current branch.

Frequently Asked Questions about feature-branch-pr-writing

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

FAQPage Schema
How do I write a pull request description for a feature branch?

You can draft a pull request description for a feature branch by analyzing the diff against the target branch and tracing related PRs to generate a structured narrative covering rationale and changes.

Can I generate PR titles in conventional commit format for multiple changes?

Yes, you can generate PR titles in conventional commit format for changes that touch multiple areas by analyzing the branch diff and summarizing the branch's intent.

How do I create a PR draft when context is missing from the branch?

To create a PR draft with missing context, the skill references linked PRs and branch state to guide questioning, prompting you for the necessary information before generating the description.

What is needed to draft a PR for a non-trunk feature branch?

Drafting a PR for a non-trunk feature branch requires an existing PR or a branch targeting a feature branch, allowing the diff analysis and related PR tracing to output a structured draft.

Does this PR writing skill work with chained pull requests?

Yes, the skill works with chained pull requests by tracing related PRs in the chain to ensure the generated PR description accurately reflects the branch state and dependencies.

When should I use an automated PR description generator?

You should use an automated PR description generator when your team adopts standardized PR conventions and needs consistent, clear narratives for rapid review of non-trunk feature branches.