skills.rest
damsac
damsacOFFICIAL
Explore all skills by this author →
GitHub

draft-pr

Draft PR descriptions by synthesizing diffs, prompt workflows, and meta entries.

Updated Feb 8, 2026
Search Tags:#documentation#workflows#code-review#pull-request#draft-pr#pr-description#meta-entries
One-click install
npx skills add https://github.com/damsac/slate --skill draft-pr-damsac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: draft-pr
Source: https://github.com/damsac/slate/tree/main/.claude/skills/draft-pr
Command: npx skills add https://github.com/damsac/slate --skill draft-pr-damsac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft PRs helps engineers create information-dense PR descriptions that explain decisions, changes, and context to reviewers.

Core Features & Use Cases

  • Analyzes changes, prompt files, and meta entries to draft comprehensive PR descriptions
  • Links relevant documentation and meta entries to educate reviewers
  • Accelerates code reviews by surfacing rationale and trade-offs

Quick Start

Ask for a draft PR description for the current branch, including decisions and next steps.

Frequently Asked Questions about draft-pr

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

FAQPage Schema
How do I generate a pull request description that explains the rationale behind code changes?▼

Generate pull request descriptions by synthesizing repository diffs, prompt workflows, and meta entries into an information-dense narrative. This approach clearly explains what changed and why, providing reviewers with necessary context and traceability.

Can I draft PR descriptions for documentation updates and bug fixes, not just feature branches?▼

Yes, you can draft PR descriptions for documentation updates and bug fixes. The synthesis of diffs, prompt workflows, and meta entries applies to any branch requiring context, rationale, and traceability to prompt decisions.

What is the best way to link related documentation in a PR description without duplicating it?▼

The best way to link related documentation in a PR description is by synthesizing meta entries and prompt workflows to reference existing materials. This emphasizes linking to related documentation rather than duplicating content, educating reviewers efficiently.

How do I use meta entries and prompt workflows to accelerate code review?▼

Accelerate code review by using meta entries and prompt workflows to draft PR descriptions that surface rationale and trade-offs. Analyzing repository changes alongside the workflows/prompts directory provides reviewers with decisions and context.

Do I need a workflows/prompts directory to draft information-dense PR narratives?▼

Yes, the repository relies on the workflows/prompts directory and existing meta entries to draft information-dense PR narratives. These sources provide the prompt decisions and traceability needed to explain what changed and why.

When should I avoid automatically drafting PR descriptions from diffs and meta entries?▼

Avoid automatically drafting PR descriptions when repository changes lack corresponding meta entries or prompt workflows. Without these sources to provide context, rationale, and traceability, the generated narrative may fail to educate reviewers properly.

Related Skills

Explore More Software Engineering Skills→
lluppesmslluppesms

suggest-awesome-github-copilot-prompts

Suggest relevant GitHub Copilot prompts from the awesome-copilot repository.

Community
Intermediate
justifi-techjustifi-tech
5

pr-review

Automate GitHub PR reviews with size checks and gh pr review actions.

Official
Advanced
agnaldo4jagnaldo4j
1

wiki-maintenance

Map code changes to GitHub wiki pages and enforce update workflows.

Community
Advanced
mindspore-aimindspore-ai
258

akg-pr

Generate AKG PR descriptions and validation artifacts from branch diffs.

Official
Intermediate