heroesofcode/pr-summary
.cursor/skills/pr-summary/SKILL.md
Reviews local git changes and generates a pull request summary following the project template. Use when the user asks to automate PR summary, generate PR description, fill PR template, or review local changes for a PR.
$ install --global
skillsauthnpx skillsauth add heroesofcode/swift-explorer pr-summaryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 1:37 AM27.0s1 file scanned
SKILL.md
- name:
- pr-summary
- description:
- Reviews local git changes and generates a pull request summary following the project template. Use when the user asks to automate PR summary, generate PR description, fill PR template, or review local changes for a PR.
PR Summary from Local Changes
Generates a PR description that matches .github/pull_request_template.md by analyzing the repository's local changes (staged and/or unstaged).
Workflow
-
Gather change context
- Run
git statusto see modified/added/deleted files and current branch. - Run
git diff --stagedfor staged changes; if empty, rungit difffor unstaged changes (or both if the user wants everything). - Optionally run
git log -1 --onelineorgit log origin/main..HEAD --onelineto see recent commits on the branch.
- Run
-
Infer type of change From the diff and file list, choose one or more types that fit:
- Enhancement – improvements to existing behavior
- Bug fix – fixes to incorrect behavior
- Security fix – security-related changes
- Breaking change – API or behavior changes that break compatibility
- New feature – new functionality
- New release – version/release bumps or release notes
- Documentation – docs, comments, README only
- Refactor – restructuring without changing behavior
-
Write the summary as topic bullets
- Use only bullet points (topics), no paragraph text.
- One short line per change, e.g. "add ...", "fix ...", "update ...", "remove ...".
- No extra explanation; keep each line concise.
-
Output in template format Use this structure (from the project template). Replace the summary text and check the applicable type(s).
-
Deliver the result
- Reply with the PR summary in a markdown code block (so the user can copy it from the chat).
- Also write the same content to
pr-description.mdin the repository root so the user can open the file and copy from there. Tell the user the file path; they can delete the file after pasting into the PR.
Output Template
Use this exact structure. Under "Summary", list only bullet-point topics (no paragraph). In "Type of Change", check only the box(es) that apply (use [x] for checked, [ ] for unchecked).
## ✨ Summary
- <topic 1>
- <topic 2>
- ...
## 🔧 Type of Change
- [ ] ✨ Enhancement
- [ ] 🐞 Bug fix
- [ ] 🔐 Security fix
- [ ] 💥 Breaking change
- [ ] 🚀 New feature
- [ ] 📦 New release
- [ ] 📚 Documentation
- [ ] ♻️ Refactor
Example
After reviewing a diff that adds a new Swift API and updates README:
## ✨ Summary
- add public `validate(input:)` method
- update README with usage docs
## 🔧 Type of Change
- [ ] ✨ Enhancement
- [ ] 🐞 Bug fix
- [ ] 🔐 Security fix
- [ ] 💥 Breaking change
- [x] 🚀 New feature
- [ ] 📦 New release
- [x] 📚 Documentation
- [ ] ♻️ Refactor
Notes
- If there are no local changes, say so and suggest running from a branch with changes or staging files first.
- Prefer the project template at
.github/pull_request_template.mdif it diverges from the template above; the template in this skill matches the current project standard.
Related Skills
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,764SKILL.mdUpdated Apr 10, 2026
steipete/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,588SKILL.mdUpdated Apr 13, 2026
steipete/xurl
tools
VerifiedTrustedCommunity
A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.
356,423SKILL.mdUpdated Apr 13, 2026