pr-summary
Generates a structured Pull Request (PR) summary, including the PR title, a list of changes, an optional test plan, and linked issue numbers. It streamlines the creation of consistent and comprehensive PR descriptions.
About this skill
The `pr-summary` skill is designed to automate the creation of well-formatted Pull Request descriptions. It takes a series of inputs such as the PR title, an array of changes implemented, an optional array of test plan items, and an optional array of related issue numbers. The skill then processes these inputs and generates a neatly structured Markdown string that is ready to be used as a PR description. This skill is particularly beneficial for developers and teams aiming to standardize their code review process and improve documentation consistency. By automating the summary generation, it ensures that all essential information — what was changed, how it was tested, and which issues it addresses — is consistently included in every pull request, reducing manual effort and potential oversight. Users would leverage this skill to save time when drafting PRs, enhance the clarity and completeness of their code contributions, and facilitate smoother code reviews. It helps maintain a high standard of communication within development teams and ensures that PRs are always linked back to their respective tasks or bugs, improving project traceability and management.
Best use case
The primary use case for `pr-summary` is to standardize and automate the generation of pull request descriptions within a software development workflow. Developers, particularly those in teams that prioritize consistent documentation and efficient code reviews, benefit significantly by quickly producing clear, comprehensive, and uniformly formatted PR summaries, reducing manual drafting time and ensuring all critical information is present.
Generates a structured Pull Request (PR) summary, including the PR title, a list of changes, an optional test plan, and linked issue numbers. It streamlines the creation of consistent and comprehensive PR descriptions.
A well-formatted, Markdown-based string containing a summary of your pull request, including changes, test plan, and related issues, ready for use in a PR description field.
Practical example
Example input
{"title": "Fix: Implement robust error handling for API endpoints", "changes": ["Added try-catch blocks to all critical API routes", "Standardized error response format (JSON)", "Implemented custom error middleware"], "testPlan": ["Verify all existing API endpoints still function correctly", "Test custom error messages for various failure scenarios", "Ensure proper logging of errors"], "issues": [201, 205]}Example output
## Summary Fix: Implement robust error handling for API endpoints ## Changes - Added try-catch blocks to all critical API routes - Standardized error response format (JSON) - Implemented custom error middleware ## Test Plan - [ ] Verify all existing API endpoints still function correctly - [ ] Test custom error messages for various failure scenarios - [ ] Ensure proper logging of errors ## Related Issues - Closes #201 - Closes #205 --- 🤖 Generated with [Claude Code](https://claude.com/claude-code)
When to use this skill
- When submitting a new pull request for code review.
- To ensure consistent and comprehensive formatting for all PR descriptions.
- When linking a pull request to specific issues or tasks in a project tracker.
- To quickly generate a structured test plan alongside your code changes.
When not to use this skill
- When the PR description requires a completely custom or free-form format not supported by the skill's inputs.
- When you need to interact directly with a Git platform's API (e.g., creating the PR itself, merging, commenting).
- When only a very brief, informal summary is sufficient and structure is not a concern.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/pr-summary/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How pr-summary Compares
| Feature / Agent | pr-summary | Standard Approach |
|---|---|---|
| Platform Support | Claude | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | easy | N/A |
Frequently Asked Questions
What does this skill do?
Generates a structured Pull Request (PR) summary, including the PR title, a list of changes, an optional test plan, and linked issue numbers. It streamlines the creation of consistent and comprehensive PR descriptions.
Which AI agents support this skill?
This skill is designed for Claude.
How difficult is it to install?
The installation complexity is rated as easy. You can find the installation instructions above.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
Top AI Agents for Productivity
See the top AI agent skills for productivity, workflow automation, operational systems, documentation, and everyday task execution.
SKILL.md Source
# pr-summary
Creates comprehensive Pull Request summaries with changes, test plan, and related issues.
## Metadata
- **Version**: 1.0.0
- **Category**: git-workflow
- **Source**: workspace
## Tags
`git`, `pull-request`, `github`
## MCP Dependencies
None specified
## Inputs
- `title` (string) (required): PR title
- `changes` (array) (required): List of changes made
- `testPlan` (array) (optional): Test plan items
- `issues` (array) (optional): Related issue numbers
## Workflow
No workflow defined
## Anti-Hallucination Rules
None specified
## Verification Checklist
None specified
## Usage
```typescript
// Execute via MCP Gateway:
gateway_execute_skill({ name: "pr-summary", inputs: { ... } })
// Or via REST API:
// POST /api/code/skills/pr-summary/execute
// Body: { "inputs": { ... } }
```
## Code
```typescript
const { title, changes, testPlan = ['Verify tests pass', 'Manual testing'], issues = [] } = inputs;
let pr = `## Summary\n${title}\n\n## Changes\n`;
for (const c of changes) pr += `- ${c}\n`;
pr += `\n## Test Plan\n`;
for (const t of testPlan) pr += `- [ ] ${t}\n`;
if (issues.length > 0) {
pr += `\n## Related Issues\n`;
for (const i of issues) pr += `- Closes #${i}\n`;
}
pr += `\n---\n🤖 Generated with [Claude Code](https://claude.com/claude-code)`;
console.log(pr);
```
---
Created: Mon Dec 22 2025 10:36:14 GMT+0800 (Singapore Standard Time)
Updated: Mon Dec 22 2025 10:36:14 GMT+0800 (Singapore Standard Time)Related Skills
ai-pair
AI Pair Collaboration Skill. Coordinate multiple AI models to work together: one creates (Author/Developer), two others review (Codex + Gemini). Works for code, articles, video scripts, and any creative task. Trigger: /ai-pair, ai pair, dev-team, content-team, team-stop
review
Daily and weekly review workflows. USE WHEN user says "morning routine", "evening routine", "weekly review", "start my day", "end of day".
Beads Issue Tracking Skill
> **Attribution**: [Beads](https://github.com/steveyegge/beads) by [Steve Yegge](https://github.com/steveyegge)
prd
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
Skill: Runs
## Purpose
Claude-Zeroclaw SKILL
## Overview
reprompter
Transform messy prompts into structured, effective prompts — single, multi-agent, or reverse-engineered from great outputs. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags, "reprompter teams", "repromptverse", "run with quality", "smart run", "smart agents", "campaign swarm", "engineering swarm", "ops swarm", "research swarm", multi-agent tasks, audits, parallel work, "reverse reprompt", "reprompt from example", "learn from this", "extract prompt from", "prompt dna", "prompt genome", reverse-engineering prompts from exemplar outputs. Don't use for simple Q&A, pure chat, or immediate execution-only tasks (see "Don't Use When" section). Outputs: structured XML/Markdown prompt, before/after quality score, optional team brief + per-agent sub-prompts, Agent Cards, Extraction Card (reverse mode). Target quality score: Single ≥ 7/10; Repromptverse per-agent ≥ 8/10; Reverse ≥ 7/10.
session-pack
세션 종료 시 Memory, Handoff를 자동 정리. /pack
execute
Main entry point for hierarchical task execution. Orchestrates layer-by-layer implementation of PRD tasks with parallel worktree execution.
textum
Textum PRD→Scaffold→Story workflow for Codex with low-noise outputs and gate checks.
sdd
This skill should be used when users want guidance on Spec-Driven Development methodology using GitHub's Spec-Kit. Guide users through executable specification workflows for both new projects (greenfield) and existing codebases (brownfield). After any SDD command generates artifacts, automatically provide structured 10-point summaries with feature status tracking, enabling natural language feature management and keeping users engaged throughout the process.
nonstop
Enables an autonomous work mode for AI agents, allowing continuous operation without user interruption. It includes a pre-flight risk assessment and intelligent blocker handling to maximize productivity.