Automated summary
Analyzes pull request changes to provide a comprehensive summary with context, impact analysis, and review guidance.
Strengths
- Generates a structured and scannable summary of changes
- Highlights impact on the codebase and potential risks
- Guides reviewers toward critical areas needing attention
- Produces a concise one-liner suitable for changelogs
Limitations
- Requires the `gh` CLI tool to be installed and authenticated
- Works only with GitHub repositories
- Quality depends on the clarity of the PR description and comments
When you need to quickly understand a pull request, prepare a review, or generate release notes.
For extremely large PRs where the diff alone does not capture full context.
Security analysis
SafeThe skill only runs read-only gh commands to fetch PR metadata, diff, and comments. No destructive actions, exfiltration, or obfuscation are present. Bash is used solely to invoke gh in a controlled manner.
No concerns found
How this analysis is madeExamples
Summarize this pull request with impact analysis and review guidance.Analyze the changes in PR #42 and provide a review guide highlighting risks.name: pr-summary description: Summarizes pull request changes with context, impact analysis, and review guidance. Use when reviewing PRs, onboarding to a PR, or preparing release notes. context: fork agent: Explore allowed-tools: Bash(gh *)
Pull request context
- PR metadata: !
gh pr view --json title,body,author,baseRefName,headRefName,additions,deletions,changedFiles - PR diff: !
gh pr diff - PR comments: !
gh pr view --comments - Changed files: !
gh pr diff --name-only
Your task
Analyze this pull request and provide a comprehensive summary:
1. Overview
- What is this PR trying to accomplish?
- What problem does it solve or feature does it add?
2. Changes breakdown
- Group changes by category (e.g., features, fixes, refactoring, tests, docs)
- Highlight the most significant changes
- Note any deleted or deprecated code
3. Impact analysis
- What parts of the codebase are affected?
- Are there any breaking changes?
- What dependencies or downstream systems might be impacted?
4. Review guidance
- What areas deserve the closest review?
- Are there any potential concerns or risks?
- What tests or validations should be performed?
5. One-line summary
- Provide a concise summary suitable for release notes or changelog
Keep the summary scannable with bullet points. Focus on the "why" and "what", not just listing files changed.
Design-to-Dev Specification Writer
Development
Translate your mockups into technical specifications for developers.
Exports & Barrel Files
Development
Defines conventions for module exports and barrel files: named exports only, no flat wildcards (except `export * as Name` for compound components), sectioned comments, types alongside values, and one export line per source file. Helps maintain consistent, tree-shakeable exports in portal apps using Turbopack or similar bundlers.
Write an Agent Skill
Development
Step-by-step guide to create a structured Agent Skill for coding agents, including directory structure, SKILL.md format, and design principles.