open-source-contributions

Enforce Conventional Commits, pre-PR checks, and branch hygiene for pull requests.

33|12|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/durabullhq/durabull --skill open-source-contributions-durabullhq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-source-contributions
Source: https://github.com/durabullhq/durabull/tree/main/.agents/skills/open-source-contributions
Command: npx skills add https://github.com/durabullhq/durabull --skill open-source-contributions-durabullhq

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Creates a standardized, maintainer-friendly PR process by embedding best-practice guidelines, automated checks, and templates to reduce rejection risk and review time.

Core Features & Use Cases

  • Guidance on PR scope and commit hygiene to keep changes focused
  • Pre-PR checks, templates, and documentation updates to streamline reviews
  • Structured, reusable scripts (pre-pr-check.sh, clean-branch.sh) to enforce quality
  • Use Cases: new feature PRs, bugfix PRs, documentation updates, and refactors with minimal noise

Quick Start

Run the pre-PR check script to validate your branch before submitting a PR.

Frequently Asked Questions about open-source-contributions

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

FAQPage Schema
How do I prepare a pull request to pass maintainer code review?

Run pre-PR checks to validate branch hygiene and conventional commits before submitting a pull request. This enforces documentation, tests, and code standards to ensure focused changes that reduce rejection risk and streamline reviews.

What is a pre-PR check and how does it streamline open source contributions?

A pre-PR check is an automated validation step that enforces project contribution standards before submitting a pull request. It verifies conventional commits, branch hygiene, and documentation updates to reduce review time and prevent rejections.

How do I enforce conventional commits for branch management before submitting a PR?

Enforce conventional commits for branch management by running a clean-branch script. This ensures focused commit hygiene and validates that your branch meets documentation and test standards before you create a pull request.

Does this PR preparation process work for documentation updates and refactors?

Yes, this PR preparation process works for documentation updates and refactors. It applies pre-PR checks and templates to ensure minimal noise and focused changes across new features, bugfixes, and documentation changes alike.

Why do my pull requests get rejected and how can I prevent it?

Pull requests often get rejected due to poor commit hygiene or missing documentation. Prevent rejections by running automated pre-PR checks that enforce conventional commits, branch hygiene, and test standards before submission.