This skill generates and improves GitHub pull request descriptions that help reviewers understand context and promote effective code reviews. Use this skill when creating new PRs, updating PR descriptions with new commits, or reviewing existing PR descriptions for quality. The skill analyzes git commits to extract key changes and generates descriptions with proper context (why), implementation details (how), file prioritization for large PRs, and testing strategy.
Analyzes your git commits to generate comprehensive PR descriptions with context, implementation details, and testing guidance. Use when creating new PRs, updating descriptions after new commits, or reviewing existing PRs for quality.
/plugin marketplace add simonlee2/claude-plugins/plugin install git-workflow@simon-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
assets/example_good_pr.mdassets/example_weak_pr.mdassets/pr_template.mdreferences/pr_description_guide.mdscripts/analyze_git_commits.pyThis skill generates comprehensive, reviewer-friendly pull request descriptions by analyzing git commits and changes. It helps authors communicate their changes effectively, enabling reviewers to understand context, give better feedback, and spend less time orienting themselves to the code.
The skill handles three main scenarios:
User request: "Write a PR description for my changes"
What Claude will do:
scripts/analyze_git_commits.py to analyze commits and file changesreferences/pr_description_guide.md for best practicesWhat to expect:
User request: "Update the PR description to reflect the new commits I just added"
What Claude will do:
What to expect:
User request: "Review this PR description for quality" or "Improve this PR description"
What Claude will do:
references/pr_description_guide.mdWhat to expect:
1. Follow the commits, don't invent The PR description is derived from what's actually in the git commits. Commit messages are the source of truth for what was changed and why.
2. Organize by importance, not just by file list For large PRs, explicitly call out which files contain critical logic that must be reviewed first. Distinguish core changes from supporting changes (tests, docs, configuration).
3. Explain the "why" before the "what" Context about business needs, design decisions, and tradeoffs is more important than a file-by-file breakdown of changes.
4. Provide actionable testing guidance Reviewers should be able to validate the changes by following the testing instructions without hunting for information.
Python script that analyzes git commits and changes to extract structured information:
Run this script to gather input for PR descriptions.
Comprehensive guide documenting:
This is the authoritative reference for PR description best practices.
Example PR descriptions showing best practices:
pr_template.md – Basic template structureexample_good_pr.md – Comprehensive example of a well-written PR description with all sections properly filledexample_weak_pr.md – Example of weak description before improvement, with annotations on what's wrong and how to fix itUse these examples to understand the expected level of detail and structure.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.