pr-draft-summary

Generate a PR-ready title and description from git state.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/yuichi176/artlyst --skill pr-draft-summary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-draft-summary
Source: https://github.com/yuichi176/artlyst/tree/main/.codex/skills/pr-draft-summary
Command: npx skills add https://github.com/yuichi176/artlyst --skill pr-draft-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly generate a pull request draft that includes a concise change summary, a PR-ready title, and a ready-to-submit description after substantive code changes.

Core Features & Use Cases

  • Automatic git-state capture: Detects current branch, changed files, and untracked assets.
  • PR block generation: Produces a ready-to-submit title and description for the PR.
  • Branch recommendation: Suggests a descriptive branch name based on the changes.
  • Use Case: After completing a large refactor, generate the PR documentation to accelerate review.

Quick Start

Invoke the pr-draft-summary skill in your repository after substantive code work is complete to generate the PR draft block. The tool will collect git state, compute a lead change type, propose a branch name, and render the PR title and description.

Frequently Asked Questions about pr-draft-summary

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

FAQPage Schema
How do I generate a pull request summary after completing code changes?

Pull request summaries are generated automatically after substantive code work by capturing your git state, analyzing changed files, and producing a ready-to-submit PR title and description. Invoke the skill in your repository when code changes are complete to output the PR draft block.

What information does the PR draft include?

The PR draft includes a concise change summary, a PR-ready title, a full description for review, a recommended branch name based on changes, and detection of current branch, modified files, and untracked assets from your git state.

When should I use PR draft generation in my workflow?

Use PR draft generation after completing substantive changes to runtime code, tests, examples, documentation with behavior impact, or build and test configuration—before submitting your work-complete response or pushing to your repository.

Does this work with code review workflows?

Yes, PR draft generation integrates into code review workflows by automating the creation of PR documentation that accelerates review cycles. The generated title and description help reviewers understand changes quickly and reduce back-and-forth on PR setup.

What types of code changes does PR draft handle?

PR draft handles runtime code modifications, test additions or updates, example file changes, documentation with behavior impact, and build or test configuration changes. It computes a lead change type to recommend the most relevant branch name and summary framing.