
Pr Description Writer
Generate structured pull request descriptions from diffs and commit history
What You Can Do
You can automatically generate comprehensive pull request descriptions from your code changes, commit history, and diffs. The skill produces structured PR bodies that communicate the rationale behind changes, step-by-step testing procedures, key review focus areas, and placeholder sections for UI screenshots—significantly reducing review cycles and clarification requests.
Features
Generates clear summaries of modifications at component and module level
Synthesizes business rationale, issue references, and architectural decisions from commit messages
Creates step-by-step reproduction and validation procedures for reviewers
Highlights critical code paths, potential risks, and areas requiring scrutiny
Includes structured sections for screenshots and UI/UX documentation
Outputs PR descriptions following platform conventions and markdown best practices
Handles complex refactors, multi-service changes, and subsystem impacts
Flags deprecations and migration guidance when applicable
Example Output
What Changed Refactored authentication middleware to use JWT token validation instead of session-based auth. Updated 8 endpoints across the auth service and user service to support both legacy and new token formats.
Why Resolves #4521. Improves security posture by eliminating session storage vulnerability and enables stateless API scaling.
How to Test
- Run
npm test auth.middleware.spec.jsto verify token validation logic - Start dev server:
npm run dev - Call POST /api/login with valid credentials, verify JWT is returned
- Use returned token in Authorization header for subsequent requests
- Test token expiry by advancing system clock 1 hour, requests should fail
Review Focus
- ⚠️ Token refresh logic in
refreshToken()— verify expiry calculations match spec - ⚠️ Backward compatibility layer — test with legacy session tokens
- ✅ Performance: No DB queries added to auth path
Screenshots [Login flow updated to return JWT instead of session ID]
What's Included
- SKILL.md instruction file with overview and usage guidelines:
- PR Description Template: structured markdown sections ready for customization
- Diff Analysis Framework: guidance on extracting key changes from git diffs
- Testing Procedure Checklist: common test scenarios and validation steps
- Review Focus Worksheet: prompts to identify critical areas and potential risks
Who It's For
- Software Engineers & Developers — need to write clear PRs for team review
- Engineering Leads & Tech Leads — review complex cross-service changes and mentor on PR clarity
- DevOps Engineers — document infrastructure changes and deployment procedures
- Code Review Champions — enforce PR documentation standards across teams
- Open Source Maintainers — reduce friction in community contribution reviews
Best For
- Complex refactors spanning multiple files or modules
- Cross-service or multi-system changes requiring architectural context
- UI/UX changes needing visual documentation and testing procedures
- Breaking changes and deprecations requiring migration guidance
- Performance-impacting changes where optimization strategy must be clear
- API contract changes affecting multiple consumers
- Security-related modifications requiring detailed review justification







