open-source-contributions

Scan branches for personal artifacts and validate pull request quality.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/brendadeeznuts1111/tier-1380-omega --skill open-source-contributions-brendadeeznuts1111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-source-contributions
Source: https://github.com/brendadeeznuts1111/tier-1380-omega/tree/main/skills/open-source-contributions
Command: npx skills add https://github.com/brendadeeznuts1111/tier-1380-omega --skill open-source-contributions-brendadeeznuts1111

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you avoid common mistakes that lead to pull request rejection or delays, ensuring your contributions are professional and maintainer-friendly.

Core Features & Use Cases

  • Artifact Cleanup: Automatically detects and helps remove personal development files (like SESSION.md, planning docs, debug screenshots) before submission.
  • Quality Validation: Checks for secrets, large files, and adherence to PR size limits.
  • Guidance: Provides templates and best practices for PR descriptions, commit messages, and communication.
  • Use Case: Before submitting a PR to a new open-source project, you can run this Skill to ensure you haven't accidentally included sensitive information or personal notes, and that your PR follows the project's contribution guidelines.

Quick Start

Run the pre-PR check script to scan your branch for common mistakes.

Frequently Asked Questions about open-source-contributions

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

FAQPage Schema
How do I remove personal development artifacts before submitting a pull request?

To avoid pull request rejection, scan your branch for personal development artifacts, secrets, and large files. This validates your PR quality against common mistakes and ensures your contribution is professional and maintainer-friendly.

How do I ensure my GitHub pull request follows best practices?

To ensure your GitHub pull request follows best practices, validate your branch for sensitive information and large files. Then apply provided markdown templates for commit messages and PR descriptions to align with project contribution guidelines.

What is included in a maintainer-friendly pull request?

A maintainer-friendly pull request includes a validated branch free of personal artifacts, secrets, and large files. It also utilizes provided templates for commit messages and PR descriptions to ensure clear communication and adherence to project guidelines.

Can I automatically scan my git branch for common PR mistakes?

Yes, you can automatically scan your git branch for common PR mistakes using bash file scanning scripts. This detects personal development artifacts, validates PR size limits, and checks for secrets to ensure your pull request is ready for submission.

Does this process check for secrets and large files in my code?

Yes, the quality validation process checks for secrets and large files in your code. It validates your branch against common PR mistakes to ensure sensitive information is removed and appropriate PR size limits are maintained before submission.