/pr-summary
Summarize current pull request with diff, comments, and changed files. Use when reviewing PRs or before merging.
$ npx -y skills add fusengine/agents --skill pr-summary --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/pr-summary
Context preview
The summary Claude sees to decide when to auto-load this skill.
Summarize current pull request with diff, comments, and changed files. Use when reviewing PRs or before merging.
SKILL.md
pr-summary.SKILL.mdname: pr-summary
description: Summarize current pull request with diff, comments, and changed files. Use when reviewing PRs or before merging.
argument-hint: "[pr-number]"
context: fork
agent: fuse-ai-pilot:explore-codebase
disable-model-invocation: false
user-invocable: true
<objective> PR Summary produces a structured overview of the current pull request from `gh pr diff`, `gh pr view --comments`, and `gh pr status`: what the PR does, the key file-level changes, potential risks (breaking changes, security concerns), and what a reviewer should check carefully. It runs in a forked context via the `explore-codebase` agent so the full diff and comment thread don't pollute the parent conversation. </objective>
PR Summary Skill
Summarize the current pull request.
Pull Request Context
- **PR diff:** !`gh pr diff`
- **PR comments:** !`gh pr view --comments`
- **Changed files:** !`gh pr diff --name-only`
- **PR status:** !`gh pr status`
Task
Analyze this pull request and provide:
1. **Overview** - What does this PR do? 2. **Key Changes** - Main files and modifications 3. **Potential Risks** - Breaking changes, security concerns 4. **Review Recommendations** - What to check carefully
Output Format
## PR Summary: [Title]
### Overview
[1-2 sentences]
### Key Changes
- [file]: [change description]
- ...
### Risks
- [risk if any]
### Recommendations
- [what to verify]
Debug
- Session: ${CLAUDE_SESSION_ID}
- Timestamp: !`date +%Y-%m-%d_%H:%M:%S`
Read more
name: pr-summary description: Summarize current pull request with diff, comments, and changed files. Use when reviewing PRs or before merging. argument-hint: "[pr-number]" context: fork agent: fuse-ai-pilot:explore-codebase disable-model-invocation: false user-invocable: true
<objective> PR Summary produces a structured overview of the current pull request from `gh pr diff`, `gh pr view --comments`, and `gh pr status`: what the PR does, the key file-level changes, potential risks (breaking changes, security concerns), and what a reviewer should check carefully. It runs in a forked context via the `explore-codebase` agent so the full diff and comment thread don't pollute the parent conversation. </objective>
PR Summary Skill
Summarize the current pull request.
Pull Request Context
- **PR diff:** !`gh pr diff`
- **PR comments:** !`gh pr view --comments`
- **Changed files:** !`gh pr diff --name-only`
- **PR status:** !`gh pr status`
Task
Analyze this pull request and provide:
1. **Overview** - What does this PR do? 2. **Key Changes** - Main files and modifications 3. **Potential Risks** - Breaking changes, security concerns 4. **Review Recommendations** - What to check carefully
Output Format
## PR Summary: [Title] ### Overview [1-2 sentences] ### Key Changes - [file]: [change description] - ... ### Risks - [risk if any] ### Recommendations - [what to verify]
Debug
- Session: ${CLAUDE_SESSION_ID}
- Timestamp: !`date +%Y-%m-%d_%H:%M:%S`
A plugin ecosystem that turns Claude Code into a supervised, multi-agent development environment.
Repo: fusengine/agents
Other skills on fusengine-agents.
- /agent-creator
Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.
Open skill - /apex-methodology
Use when starting ANY development task -- feature, bug fix, refactor, hotfix (triggers: implement, create, build, fix, add feature, refactor, develop).
Open skill - /brainstorming
Use when creating a feature/component or adding functionality. Fires BEFORE APEX Analyze to refine requirements via structured questioning.
Open skill - /challenge
Use before a root-cause, done/verified claim, irreversible action, or 2nd-time fix reaches the owner (APEX or plain conversation); also fires at every eLicit/Verify gate. Not for code correctness (use sniper).
Open skill - /code-quality
Use when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional verification (run verification FIRST, then code-quality).
Open skill - /elicitation
Use when an expert agent self-reviews and self-corrects code after the Execute phase, before sniper validation (BMAD-METHOD elicitation techniques).
Open skill

