skills.rest
juxt
juxtOFFICIAL
Explore all skills by this author →
Website𝕏@juxtproGitHub

pr

Synthesize commit history and issue comments into GitHub pull request descriptions.

10|6|Updated Feb 8, 2026
Search Tags:#code review#pull request#github#issue tracking#commit history#pr description#chalk voice
One-click install
npx skills add https://github.com/juxt/claude-plugins --skill pr-juxt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/juxt/claude-plugins/tree/main/plugins/chalk/skills/pr
Command: npx skills add https://github.com/juxt/claude-plugins --skill pr-juxt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull request descriptions often lack critical context, implementation reasoning, and consistent tone, making it hard for reviewers to understand the "why" behind changes and leading to slower, less effective review cycles.

Core Features & Use Cases

  • Chalk Voice Alignment: Automatically formats PR titles and descriptions to match the project's standardized chalk voice, ensuring consistent, clear communication across the team.
  • Context Synthesis: Distills reasoning from branch commits, conversation history, and tracked issue comments into a coherent narrative, rather than just listing code changes from the diff.
  • Edge Case Handling: Automatically includes necessary usage steps for teammates if the change requires manual action, and prompts for clarifying questions if key context is missing from available sources.
  • Use Case: For a feature branch adding read-only database secondaries, the skill pulls all chalk session notes from the related GitHub issue to build a PR description that explains tradeoffs, dead ends, and required deployment steps, instead of a generic list of changed files.

Quick Start

Use the pr skill to draft a complete pull request description for your current feature branch, incorporating all relevant context from related issues and commit history.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I write a pull request description that explains implementation reasoning instead of just listing code changes?▼

To write a pull request description that explains implementation reasoning, you can synthesize your branch commit history, conversation context, and tracked GitHub issue comments into a structured narrative that explains the tradeoffs and required steps behind the changes.

How does synthesizing commit history and issue comments improve GitHub pull request reviews?▼

Synthesizing commit history and issue comments improves GitHub pull request reviews by distilling scattered context into a coherent PR description, allowing reviewers to understand the specific implementation tradeoffs and dead ends encountered during development rather than just viewing a diff.

What is the best way to maintain a consistent chalk voice across GitHub pull request titles and bodies?▼

The best way to maintain a consistent chalk voice across GitHub pull request titles and bodies is to automatically format the generated PR descriptions to match your project's standardized communication framework, ensuring clear and uniform tone for the team.

How do I include manual deployment steps and edge case instructions in a PR description?▼

To include manual deployment steps and edge case instructions in a PR description, the drafting process automatically identifies when a change requires manual teammate action and appends the necessary usage steps, prompting for clarifying questions if key context is missing.

Can I generate a PR description directly from tracked GitHub issue comments and conversation history?▼

Yes, you can generate a PR description directly from tracked GitHub issue comments and conversation history by pulling all related session notes to build an explanation-focused narrative that covers tradeoffs, dead ends, and required deployment steps.

What should I do if key context is missing when drafting a pull request description from branch commits?▼

If key context is missing when drafting a pull request description from branch commits, the synthesis process will automatically prompt you with clarifying questions to ensure the final PR narrative contains all necessary implementation reasoning and usage steps.

Related Skills

Explore More Software Engineering Skills→
tkstangtkstang

oat-project-capture

Create an OAT project from a git branch and conversation history.

Community
Advanced
YangTaeyoungYangTaeyoung

pr-workflow

Create and manage GitHub Pull Requests with review feedback integration.

Community
Advanced
prismaprisma
419

create-pr

Generate GitHub pull requests with conventional commit titles and narrative descriptions.

Official
Advanced
AbsolutSystemsAbsolutSystems
1

ship

Generate commit messages and pull request descriptions from feature pipeline artifacts.

Official
Advanced