win20/pr-summary
agent-skills/pr-summary/SKILL.md
Generate pull request summaries and open GitHub PRs from the current branch’s git changes.
$ install --global
skillsauthnpx skillsauth add win20/dotfiles 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, 4:38 PM15.7s1 file scanned
SKILL.md
- name:
- pr-summary
- description:
- Generate pull request summaries and open GitHub PRs from the current branch’s git changes.
PR Summary
Workflow
- Analyze changes with git:
git log main..HEAD --onelinegit diff main...HEAD --stat- If needed for clarity, read the full diff with
git diff main...HEAD.
- Draft a conventional-commit title:
- Format:
<type>(<scope>): <summary> (<ticket>) - Examples:
feat(profile): add blocking feature (HAE-111)fix(onboarding): correct next button target path (HAE-222)
- If the ticket id or scope is unclear, ask for it before finalizing the title.
- Format:
- Generate a PR body with the exact structure below. Keep it concise, no extra text, and no “Generated with …” lines.
- Create the PR using
gh pr createwith the title and body.
PR Body Template
## Summary
- [1-3 bullets describing the changes]
## Changes
- [Significant changes]
- [Files modified: list paths or key files]
- [Breaking changes, if any]
## Dependencies
- [Dependencies added or updated]
## Testing Notes
- [How to test these changes (ommit if not needed or if simple change)]
Notes
- Keep all content factual and derived from the diff/log.
- If there are no breaking changes or dependencies, write
Nonerather than omitting the line.
Related Skills
win20/expo-react-native
development
VerifiedTrustedCommunity
Best practices for developing Expo SDK 54 React Native apps with Expo Router, Zustand, and NativeWind. Use when building mobile apps with this stack, implementing navigation, state management, styling, performance optimization, TypeScript patterns, or security.
1SKILL.mdUpdated Apr 16, 2026
win20/expo-react-native
development
VerifiedTrustedCommunity
Best practices for developing Expo SDK 54 React Native apps with Expo Router, Zustand, and NativeWind. Use when building mobile apps with this stack, implementing navigation, state management, styling, performance optimization, TypeScript patterns, or security.
1SKILL.mdUpdated Apr 16, 2026
win20/simplify-code
development
VerifiedTrustedCommunity
Simplify and clarify existing code without changing behavior.
1SKILL.mdUpdated Apr 16, 2026
win20/local-review
development
VerifiedTrustedCommunity
Code reviews of git changes without creating actual PR.
1SKILL.mdUpdated Apr 16, 2026