Optimize pull requests for quick approval and merging by ensuring clean diffs, comprehensive self-reviews, and structured documentation.
72%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/pr-merge-champion/SKILL.mdA systematic playbook for preparing, reviewing, and documenting pull requests to ensure they are high-quality, free of common oversights, and optimized for instant maintainer approval and merging.
Before presenting your code to reviewers, clean up any workspace noise and ensure your branch is up to date:
main or master) to resolve conflicts early.Review your own diff line-by-line as if you were the reviewer. Look out for:
console.log, print, breakpoints, or custom debug flags).TODO comments that should be resolved or turned into tracked issues.Verify that all changes work as expected:
Write a high-signal, structured PR description. A great description tells the story of the changes:
# Pull Request: Implement Rate Limiting on Authentication Endpoint
## Summary
Introduces an IP-based rate limiter on the `/api/v1/auth/login` endpoint using Redis to prevent brute-force attacks.
## Why
We identified a high volume of login attempts targeting single accounts. This rate limiting window slows down attackers while keeping the system responsive for genuine users.
## Verification
- Ran unit tests: `npm run test tests/auth.test.js` (all green)
- Manually verified using Postman: sending 15 requests in under 60 seconds returns `429 Too Many Requests`.
## Checklist
- [x] Code follows the style guide
- [x] Unit tests added/updated
- [x] Documentation updatedBefore committing, run these commands to inspect the diff for accidental additions:
# Check the names of files changed to ensure no unwanted files are staged
git status --porcelain
# Review the actual diff for any leftover print statements or debuggers
git diff | grep -E "(console\.log|debugger|print\(|var_dump|binding\.pry)"CONTRIBUTING.md and pull request templates, and adhere to them strictly.@pr-writer - For Sentry-specific PR writing guidelines.@clean-code - To ensure code quality before submitting.BigSimmo/Communication
b4de79a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.