upstream-contribution

Guides opening pull requests against third-party upstream repositories following their contribution rules.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/harivansh-afk/loom-index-e2e --skill upstream-contribution-harivansh-afk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upstream-contribution
Source: https://github.com/harivansh-afk/loom-index-e2e/tree/main/skills/upstream-contribution
Command: npx skills add https://github.com/harivansh-afk/loom-index-e2e --skill upstream-contribution-harivansh-afk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull requests to repositories you do not own get closed without review when they ignore the project's stated rules, AI policies, or process gates. This Skill walks you through every requirement before you write code, so your contribution survives process checks and reaches actual review. ## Core Features & Use Cases - Rule Discovery: Reads the upstream's CONTRIBUTING, AI policy, code of conduct, and PR templates on the default branch before any work begins. - Gate Checking: Identifies process blockers like CLA signatures, DCO sign-offs, required feature requests, vouch steps, and whether unsolicited PRs are accepted at all. - AI Disclosure Compliance: Applies the exact disclosure format each project demands, such as btop's [AI generated] tag or nix's Assisted-by: trailer. - Use Case: You fixed a bug in a forked dependency and want to send it upstream. The Skill checks the project's gates, matches their commit conventions from git log, opens a draft PR with gh, watches CI until green, and records the outcome if rejected. ## Quick Start Prepare a draft pull request to the upstream repository for my fix, following their contribution guidelines and AI disclosure policy.

Frequently Asked Questions about upstream-contribution

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

FAQPage Schema
How do I contribute a pull request to an open-source project I don't own?▼

Read the project's CONTRIBUTING.md, AI policy, code of conduct, and PR templates on the default branch first. Check process gates like CLA signatures or required feature requests, match their commit conventions, and open the PR as a draft until CI passes.

How to disclose AI assistance in a GitHub pull request?▼

Disclosure format is the upstream's choice. Some projects require an [AI generated] tag in the PR, others require an Assisted-by: or Generated-by: commit trailer. When no policy is stated, disclose AI assistance in the PR body anyway.

Why do upstream pull requests get closed without review?▼

PRs are closed on process grounds when they ignore stated rules: missing sign-offs, no prior accepted feature request, unvouched first-time contributors, or projects that reject unsolicited PRs entirely. Check these gates before writing any code.

Can I submit a patch to projects that don't use GitHub?▼

Some projects take GitLab merge requests or patches on a mailing list instead of GitHub PRs, and the gh CLI opens neither. Check where the project accepts submissions before preparing your change.

What should I do when an upstream PR is rejected?▼

Record that the PR was rejected and why, including the PR URL, where the next contributor will find it. Reopening or resubmitting the same change without that record wastes maintainer time.