Skill: PR Writer

Generates a professional PR description in Markdown format based on the ticket, plan document, rewritten commit messages, and code changes. The PR message is multi-audience: suitable for code reviewers and also serves as a record of intent.

When to Use

After rewriting commit messages (Phase 1 & 2), when you're ready to prepare a pull request for code review. Typically triggered after the user confirms the rewritten commits are acceptable.

Process Overview

1. Identify the ticket: Extracts ticket ID from branch name (e.g., PROJ-123-feature-name) or asks user
2. Gather context: Collects ticket description, acceptance criteria, and plan document content
3. Synthesize changes: Groups code changes by theme/domain (not by individual commits)
4. Generate PR description with:
   • Title: <ticket_id>: <short summary>
   • Summary: 2–3 sentences explaining what and why
   • Changes: Themed list of changes with commit type labels (feat/fix/refactor/test/docs)
   • Notes: Caveats, follow-ups, or reviewer attention points
5. Present to user via show_content tool in Markdown format