skills.rest
RockaRhymeLLC
RockaRhymeLLCOFFICIAL
Explore all skills by this author →
GitHub

Upstream PR

Create secure upstream pull requests with staged files and prohibited path checks.

2|Updated Feb 22, 2026
Search Tags:#git#workflow#contribution#security#github#pr
One-click install
npx skills add https://github.com/RockaRhymeLLC/kithkit --skill upstream-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Upstream PR
Source: https://github.com/RockaRhymeLLC/kithkit/tree/main/.claude/skills/upstream-pr
Command: npx skills add https://github.com/RockaRhymeLLC/kithkit --skill upstream-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents accidental contribution of sensitive instance-specific files to public repositories when creating pull requests from private forks.

Core Features & Use Cases

  • Safe Branching: Enforces starting PRs from the public repo's main branch, not a private instance's.
  • Targeted Staging: Guides users to explicitly stage only intended files, avoiding accidental inclusions.
  • Prohibited Path Enforcement: Lists specific directories and file patterns that must never be committed to a public PR.
  • Use Case: You've made changes in your private Kithkit instance and need to contribute a bug fix to the main RockaRhymeLLC/kithkit repository. This skill ensures you don't accidentally include your instance's configuration or data in the PR.

Quick Start

Follow the mandatory workflow to create a safe upstream PR for your changes.

Frequently Asked Questions about Upstream PR

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

FAQPage Schema
How do I create a GitHub pull request from a private fork without exposing sensitive instance files?▼

To create a secure pull request, you must start from the public repository's main branch, explicitly stage only the intended files, and verify that no prohibited instance-specific paths are included before submitting.

How does safe branching prevent accidental data leaks in upstream contributions?▼

Safe branching prevents data leaks by enforcing that PR branches originate from the public repository's main branch rather than your private instance, isolating public changes from private configuration and data.

What is the best way to stage files for a public repository contribution?▼

The best way to stage files is through targeted staging, which requires explicitly adding only the specific files intended for the PR while enforcing checks against committing prohibited directories and sensitive instance-specific patterns.

Can I contribute bug fixes from my private instance to the main public repository safely?▼

Yes, you can contribute safely by following a strict multi-step workflow that isolates changes on a clean branch, enforces targeted file staging, and runs prohibited path checks to prevent sensitive data exposure.

What types of files are blocked from being committed to a public PR?▼

Prohibited path enforcement blocks specific directories and instance-specific file patterns that contain private configuration or data, ensuring they are never accidentally committed to a public pull request.

Related Skills

Explore More Software Engineering Skills→
kirvinkirvin

sync

Fetch upstream changes and rebase the current Git branch onto them.

Community
Intermediate
gesmith0606gesmith0606

gsd-ship

Push branches and create pull requests with auto-generated bodies and reviewer assignment.

Community
Intermediate
camoneartcamoneart
5

Creating Atomic PRs

Create atomic pull requests with branch protection and conventional commit prefixes.

Community
Basic
dmzoneilldmzoneill
2

hotfix

Cherry-pick a commit from a development branch to a release branch.

Community
Intermediate