oss-contribution-best-practiceslisted

# Open Source Contribution Best Practices **Reference:** Based on [opensource.guide](https://opensource.guide/how-to-contribute/) This skill is the index. The detail topics live in two sibling skills that load on demand: - **`pr-etiquette`** — responding to code review feedback, writing PR descriptions, dormant-PR follow-up cadence, PR quality checklist, communication etiquette. - **`contribution-ethics`** — AI attribution rules, AI-tell avoidance in maintainer-visible writing, when to defer to a human. Both are linked below. Use this file for the universal rules that apply to every contribution regardless of stage; jump to the sibling skills when you're at a specific stage in the cycle. ## Core Principles **Be a good open source citizen:** 1. Respect maintainers' time — they're often unpaid volunteers 2. Read contribution guidelines before contributing 3. Communicate clearly and professionally 4. Be patient — open source moves at its own pace 5. Give back to the community when you can ## Minimal Diff Discipline Every line in a PR diff must be directly related to the issue being fixed. Unrelated formatting changes (whitespace, quote style, trailing commas, import reordering, line breaks) make diffs noisy, harder to review, and signal carelessness. Maintainers will flag or reject PRs with formatting bloat. **Rules:** 1. **Only touch lines the fix requires.** Don't reorder imports, change quote styles, fix whitespace, or add trailing commas in existing code — unless