The checklist I use before sending a small OSS PR

Short summary

Small PRs require discipline before coding: reproduce the bug, find the minimal fix, add focused tests, keep changes narrow. Re-read your diff through a maintainer's eyes—if the PR body needs paragraphs explaining scope, it's too wide. This pattern applies across different projects: one focused change removes one sharp edge and builds maintainer trust.

• •Reproduce issues and identify the minimal behavioral boundary before changing code
• •Keep patches narrow and focused; resist the temptation to clean up nearby code
• •Write PRs for maintainers, not as a resume—one focused change builds more trust than system-wide improvements

Generated with AI, which can make mistakes.