open-source-contributions

Pull request quality depends on removing personal artifacts, following conventional commits, validating scope, and including clear documentation. This Skill automates those checks with pre-PR cleanup templates, commit-message validation, and PR description templates aligned to maintainer expectations.

Remove debug code, temporary files, unrelated changes, and personal configuration. Verify commit messages follow conventional format, check PR size stays within project limits, ensure secrets aren't exposed, and update relevant documentation. Pre-PR scripts catch these before submission.

Conventional commits follow the format: type(scope): description. Common types are feat, fix, docs, style, refactor, test, chore. This structure makes commit history machine-readable and helps maintainers generate changelogs. Templates and guidance ensure your commits match project standards.

Yes. First-time contributors benefit most from pre-PR validation because it eliminates common rejection reasons: unclear commit messages, oversized PRs, and missing documentation. Templates and checklists guide you through each step of professional contribution.

Use the same cleanup and validation workflow to prepare your revised PR. Re-run artifact checks, verify commit hygiene, confirm PR scope and documentation are complete, then resubmit. The templates help you address feedback systematically.

Common rejection reasons: unclear or inconsistent commit messages, PRs that mix unrelated changes, missing or outdated documentation, exposed secrets or debug code, and poor communication in descriptions. This Skill eliminates these friction points through validation and templates.