How do I install the Pr Summary skill?

Run npx skillmds@latest add majiayu000/pr-summary-4 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Pr Summary skill do?

Pr Summary It is listed under Productivity on SkillMD.

Is Pr Summary safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pr Summary?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pr Summary free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pr Summary?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pr Summary by majiayu000 — Agent Skill

Name: Pr Summary
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Create PR Summary

Generate a pull request summary based on branch changes.

Instructions

Gather Context
- Get current branch name
- Find the corresponding .ai/ workflow folder for this branch:
  - For issue branches (e.g., feature/59-no-verify): look for .ai/issue-59-*
  - For named branches (e.g., feature/worktree-support): look for .ai/feature-worktree-support/ or .ai/worktree-support/
  - Use ls .ai/ and match based on branch name patterns
- Read these files if they exist (use them to understand the feature goals and implementation approach):
  - concept.md - Feature concept and design rationale
  - analysis.md - Issue analysis and requirements
  - plan.md - Implementation plan with specific changes
- Get associated issue number from branch name, commits, or analysis.md

Analyze Changes

# All commits on this branch
git log main...HEAD --oneline

# Full diff
git diff main...HEAD --stat

# Changed files
git diff main...HEAD --name-only

Generate Summary

Read .github/PULL_REQUEST_TEMPLATE.md for the format specification and example.

Use context from the .ai/ folder files to write a better summary:
- concept.md: Understand the design goals and rationale
- analysis.md: Reference the original issue requirements
- plan.md: Verify all planned changes were implemented
Write the summary to .ai/<folder>/pr_summary.md.

Create PR Command

Output the gh pr create command:

gh pr create --title "<title>" --body "$(cat .ai/<folder>/pr_summary.md)"

Report Completion
- Show path to pr_summary.md
- Show the PR creation command
- Remind to push branch first if not already pushed

PR Title Guidelines

Use imperative mood: "Add feature" not "Added feature"
Be specific but concise
Do NOT include the issue number in the title (it will be linked in the PR body)

---name: pr-summary-4description: Pr Summary--- # Create PR Summary Generate a pull request summary based on branch changes. ## Instructions 1. **Gather Context** - Get current branch name - Find the corresponding `.ai/` workflow folder for this branch: - For issue branches (e.g., `feature/59-no-verify`): look for `.ai/issue-59-*` - For named branches (e.g., `feature/worktree-support`): look for `.ai/feature-worktree-support/` or `.ai/worktree-support/` - Use `ls .ai/` and match based on branch name patterns - Read these files if they exist (use them to understand the feature goals and implementation approach): - `concept.md` - Feature concept and design rationale - `analysis.md` - Issue analysis and requirements - `plan.md` - Implementation plan with specific changes - Get associated issue number from branch name, commits, or analysis.md 2. **Analyze Changes** ```bash # All commits on this branch git log main...HEAD --oneline # Full diff git diff main...HEAD --stat # Changed files git diff main...HEAD --name-only ``` 3. **Generate Summary** Read `.github/PULL_REQUEST_TEMPLATE.md` for the format specification and example. Use context from the `.ai/` folder files to write a better summary: - **concept.md**: Understand the design goals and rationale - **analysis.md**: Reference the original issue requirements - **plan.md**: Verify all planned changes were implemented Write the summary to `.ai/<folder>/pr_summary.md`. 4. **Create PR Command** Output the `gh pr create` command: ```bash gh pr create --title "<title>" --body "$(cat .ai/<folder>/pr_summary.md)" ``` 5. **Report Completion** - Show path to pr_summary.md - Show the PR creation command - Remind to push branch first if not already pushed ## PR Title Guidelines - Use imperative mood: "Add feature" not "Added feature" - Be specific but concise - Do NOT include the issue number in the title (it will be linked in the PR body)

Frequently asked questions

Pr Summary