lucianghinda/pr-description
skills/pr-description/SKILL.md
Write GitHub Pull Request descriptions from branch commits. Use when user asks to write a PR description, create a PR summary, or document changes for a pull request. Analyzes git commits and diffs to produce structured PR documentation.
$ install --global
skillsauthnpx skillsauth add lucianghinda/agentic-skills pr-descriptionInstall 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 7, 2026, 2:35 AM16.8s1 file scanned
SKILL.md
- name:
- pr-description
- description:
- Write GitHub Pull Request descriptions from branch commits. Use when user asks to write a PR description, create a PR summary, or document changes for a pull request. Analyzes git commits and diffs to produce structured PR documentation.
PR Description Writer
Generate structured PR descriptions from branch commits.
Workflow
- Get commits:
git log --oneline origin/main..HEAD(fallback toHEAD~10..HEAD) - Get each commit's details:
git show <hash> --stat --format="%H%n%s%n%b" - Get each commit's diff:
git diff <hash>^..<hash> - Write PR description following the output format below
Output Format
1. Title
Single line. Use most meaningful commit subject or synthesize one. Keep short and technical.
2. Summary (2-5 bullets)
High-level changes. Each bullet concrete and verifiable.
3. Why (1-4 bullets)
Motivation, problem, or user impact. Tie to reliability, security, performance, DX, or product needs.
4. Commit-by-commit details
For EACH commit, add subsection with exact subject as heading:
What: 1-3 bullets describing concrete changes
Why: 1-2 bullets explaining motivation/tradeoffs
Notes: (optional) only for risk, migration, follow-up, or nuance
Rules:
- Preserve commit subject exactly as written
- If commit has a meaningful description use that
- If commit is noisy (formatting, rename), say so briefly
- Related commits: document each, keep later ones shorter ("follow-up", "fixup")
5. Testing
Checklist of what was done. If none provided, infer likely checks and label "Suggested".
6. Risk and rollout (2-6 bullets)
- What could break
- Where to watch
- Rollback plan (1 line)
- If breaking change, include BREAKING CHANGE callout
7. Screenshots/logs (optional)
Only if UI, behavior, or observability changed.
Style
- Direct and technical. No marketing tone.
- No fluff or jokes.
- Short sentences. Prefer bullets over paragraphs.
- Do not invent facts. Say "Likely" or "Inferred" if uncertain.
Related Skills
lucianghinda/improving-testing
testing
VerifiedTrustedCommunity
Produces practical, risk-based testing guidance and minimal test plans for features or changes. Use when user asks what to test, how to pick test cases (boundaries, permissions, state machines), how to improve weak tests, or to review existing tests. Covers equivalence partitions, boundary values, decision tables, and state transitions.
5SKILL.mdUpdated Apr 7, 2026
lucianghinda/commit-message
testing
VerifiedTrustedCommunity
Generate high-quality git commit messages following Conventional Commits and Chris Beams' Seven Rules. Infers WHY from context and provides clear guidance on structure, scope, and body content.
5SKILL.mdUpdated Apr 7, 2026
steipete/gh-issues
documentation
VerifiedTrustedCommunity
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]
356,423SKILL.mdUpdated Apr 13, 2026
steipete/wiki-maintainer
documentation
VerifiedTrustedCommunity
Maintain the OpenClaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.
356,423SKILL.mdUpdated Apr 13, 2026