open-source-contributions

Removes personal artifacts from pull requests before submission.

961|99|Updated Oct 20, 2025

Search Tags:#automation #code review #contribution #pull request #open source #GitHub

Ready to run

npx skills add https://github.com/jezweb/claude-skills --skill open-source-contributions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: open-source-contributions
Source: https://github.com/jezweb/claude-skills/tree/main/skills/open-source-contributions
Command: npx skills add https://github.com/jezweb/claude-skills --skill open-source-contributions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill eliminates the frustration and wasted time of PR rejections by automatically preventing 16 common mistakes that annoy maintainers.

Core Features & Use Cases

Artifact Cleanup: Automatically detects and removes personal development files like SESSION.md, planning documents, and debug screenshots before submission.
Quality Validation: Scans for proper PR sizing, commit messages, and documentation updates.
Use Case: When you're ready to submit a pull request, this Skill scans your branch for personal artifacts, validates PR quality, and provides professional communication templates.

Quick Start

I found the open-source-contributions skill. Let me run the pre-PR check to scan for personal artifacts and validate your PR quality before submission.

Frequently Asked Questions about open-source-contributions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent my pull request from being rejected by maintainers?▼

Pull requests get rejected for common mistakes like personal development artifacts, poor commit messages, and missing documentation. This Skill automatically scans your branch for these 16 common issues—personal files, improper sizing, undocumented changes—and validates them before submission, catching problems that annoy maintainers upfront.

What personal artifacts should I remove before submitting a pull request?▼

Personal artifacts include development files like SESSION.md, planning documents, debug screenshots, and other temporary files that don't belong in production code. The Skill detects and removes these automatically, ensuring only intentional code changes reach the maintainer's review.

Can I automate pull request validation before I submit to GitHub?▼

Yes. This Skill runs pre-submission validation scripts that check PR sizing, commit message quality, secret detection, and documentation updates. Automation catches issues locally before you push, reducing rejection cycles and speeding up merge times.

How do I write pull request descriptions that maintainers actually want to review?▼

Professional communication templates included in this Skill provide structured PR descriptions that clearly explain changes, context, and rationale. Templates ensure your message is clear and maintainer-friendly, removing friction from the review process.

What validation checks should happen before a pull request goes live?▼

Pre-submission validation covers artifact cleanup, PR size checks to prevent overwhelming reviewers, secret detection to prevent credential leaks, commit message guidelines for clarity, and documentation updates to keep code current. This Skill automates all these checks in one pass.

Does this work with pull requests to any GitHub repository?▼

Yes. The Skill applies to any public repository contribution workflow—whether you're a first-time contributor or migrating to a maintainer role. It handles the common rejection causes across different projects and maintainer expectations.