"The Checklist I Use Before Sending a Small OSS PR" — Morgan Shares Proven Practices for Minimal, Trustworthy Patches

“The checklist I use before sending a small OSS PR”

Morgan published a checklist for sending small open-source PRs on DEV Community. The checklist emphasizes reproducing the issue before changing code and keeping patches narrow to avoid overwhelming maintainers.

Why This Matters

“Small open-source PRs look easy from the outside because the diff is usually small,” writes Morgan. “The diff is not the work.” Maintainers carry entire project contexts in their heads; each extra file changed or ambiguous intent adds cognitive load that delays or derails contributions. A disciplined checklist—reproduce first, test incrementally, restrict scope—turns speculation into evidence, reducing friction across libraries from React Router to ast-grep and knip.

Key Insights

• Reproduce the issue before changing code ensures the fix targets the actual bug, not an assumption (Morgan, 2026).
• Add or adjust a focused test first when practical; this creates a safety net and clarifies intent (e.g., React Router SSR, ESLint edge cases).
• Keep the patch narrow even if nearby code is tempting to clean up; unrelated changes increase review time and risk of regressions.
• Re-read diff like the maintainer has never seen your reasoning—this surfaces missing context or unclear logic.
• If a PR body needs a paragraph explaining why half the files changed, the patch is probably too wide; good PRs prove one thing.

Practical Applications

• [Use case] Fixing a bug in an ESLint rule: add or adjust the focused test first, then keep the patch limited to that single edge case. [Pitfall] Cleaning up nearby code while fixing a different issue can introduce unrelated regressions and frustrate maintainers.
• [Use case] Patching Playwright optional chaining behavior: reproduce failure without changes, find smallest behavior boundary explaining it. [Pitfall] Writing a long explanation in PR body about why many files changed signals overreach—reviewers may reject without reading fully.

References:

• https://dev.to/morganlabs/the-checklist-i-use-before-sending-a-small-oss-pr-8fb