lvndry/pr-description
skills/pr-description/SKILL.md
Generate pull request titles and descriptions from diffs and context. Use when creating a PR, writing PR description, drafting merge request, or summarizing changes for review.
$ install --global
skillsauthnpx skillsauth add lvndry/jazz 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 6, 2026, 11:16 PM37.9s1 file scanned
SKILL.md
- name:
- pr-description
- description:
- Generate pull request titles and descriptions from diffs and context. Use when creating a PR, writing PR description, drafting merge request, or summarizing changes for review.
PR Description
Generate clear, structured pull request titles and descriptions from git diff, branch context, and linked issues.
When to Use
- User is about to open a PR or merge request
- User asks for a PR description, title, or summary of changes
- User wants to document what a branch does for reviewers
Workflow
- Gather context: Current branch, base branch,
git diff,git log, commit messages - Identify scope: Files changed, types of change (feature, fix, refactor, docs)
- Check for issues: Linked issue numbers in branch name or commits
- Draft title: Short, imperative, conventional (e.g.
feat(auth): add OAuth2 login) - Draft description: Summary, what changed, why, how to test, checklist
Title Format
Prefer conventional commits style:
<type>(<scope>): <short description>
Types: feat, fix, docs, style, refactor, test, chore
Scope: optional, e.g. auth, api, ui
Examples:
feat(auth): add Google OAuth2 loginfix(api): handle null in user lookupdocs: update README installation stepsrefactor(store): migrate to Zustand
Keep under 72 characters. No period at end.
Description Template
## Summary
[1-3 sentences: what this PR does and why]
## Changes
- [Key change 1]
- [Key change 2]
- [Key change 3]
## Related
- Fixes #123
- Relates to #456
## How to Test
1. [Step 1]
2. [Step 2]
## Checklist
- [ ] Tests added/updated
- [ ] Docs updated
- [ ] No breaking changes (or listed in description)
What to Include
Always:
- Summary that explains intent, not just file names
- List of meaningful changes (not every file)
- How to test (steps or "manual: ...")
- Related issue if any
When relevant:
- Breaking changes section
- Screenshots for UI changes
- Migration notes for DB/schema changes
- Performance or security notes
Avoid:
- Copy-pasting full diff into description
- Vague summaries ("updated stuff")
- Missing test instructions for non-trivial changes
Gathering Context
# Branch and diff
git branch --show-current
git log main..HEAD --oneline
git diff main...HEAD --stat
git diff main...HEAD # full diff for analysis
# Linked issues (from branch name or commits)
git log main..HEAD --oneline | grep -oE '#[0-9]+'
Infer scope from changed paths (e.g. src/auth/ → scope "auth"). Use commit messages to reinforce intent.
Tone
- Neutral and factual
- Reviewer-friendly: make it easy to understand scope and how to verify
- No marketing speak; no "This amazing PR adds..."
Anti-Patterns
- ❌ Title that repeats ticket number only ("JIRA-123")
- ❌ Description that is only "See commits"
- ❌ No testing steps for behavior changes
- ❌ Huge bullet list of every file touched
Related Skills
lvndry/todo
tools
VerifiedTrustedCommunity
Create and track task lists for complex multi-step work. Use when planning projects, breaking down work, tracking progress, or when a task has 3+ steps. Triggers on "plan", "todo", "task list", "break down", "step by step", or complex requests requiring multiple actions.
45SKILL.mdUpdated Apr 6, 2026
lvndry/startup-brainstorm
development
VerifiedTrustedCommunity
Brainstorm startup ideas using top-founder mental models, trend analysis, and competition research. Use when the user wants to brainstorm startup ideas, explore business opportunities, validate concepts, or think like elite founders. Triggers on "startup ideas", "business ideas", "what should I build", "startup brainstorm", "idea validation", "trends and opportunities", "think like a founder".
45SKILL.mdUpdated Apr 6, 2026
lvndry/skill-creator
tools
VerifiedTrustedCommunity
Create new Jazz skills for automating workflows. Use when the user asks to create a skill, make a skill, or wants to define custom automation behavior.
45SKILL.mdUpdated Apr 6, 2026
lvndry/persona
data-ai
VerifiedTrustedCommunity
Help users create, manage, and refine custom personas for Jazz agents. Use when the user wants to define a new communication style, character, or identity for an agent.
45SKILL.mdUpdated Apr 6, 2026