private-fork-sync

Convert a public GitHub fork to private and sync with upstream.

3|1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/soulmachine/skills --skill private-fork-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: private-fork-sync
Source: https://github.com/soulmachine/skills/tree/main/private-fork-sync
Command: npx skills add https://github.com/soulmachine/skills --skill private-fork-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of making a GitHub fork private while keeping it synchronized with its upstream parent repository.

Core Features & Use Cases

  • Private Fork Creation: Convert an existing public fork into a private one with minimal effort.
  • Synchronization: Keep the fork up-to-date by fetching new commits from the upstream parent repository.
  • Use Case: Useful for maintaining a secure copy of a repository where contributions are not publicly shared, yet you need to stay in sync with upstream changes.

Quick Start

Use the 'private-fork-sync' skill to make your GitHub fork private and keep it synced with its upstream parent.

Frequently Asked Questions about private-fork-sync

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

FAQPage Schema
How do I make a public GitHub fork private while keeping it synced with upstream?

To make a public GitHub fork private while keeping it synced, you can convert the fork to a private repository and fetch new commits from the upstream parent repository. This requires authentication and a local clone of the fork.

What is the best way to keep a private fork synchronized with its parent repository?

Keeping a private fork synchronized with its parent repository involves fetching new commits from the upstream repository. This ensures your secure copy stays updated with upstream changes without exposing your local modifications.

Why do I need a local clone to convert my GitHub fork to a private repository?

You need a local clone to convert your GitHub fork to a private repository because the synchronization process requires local Git operations to fetch and merge upstream changes securely.

Can I use GitHub repository management to sync a private fork automatically?

GitHub repository management allows syncing a private fork by fetching upstream changes. This Skill facilitates the process by applying authentication to securely pull new commits from the parent repository into your private copy.

When do I need to convert a fork to a private repository instead of keeping it public?

You need to convert a fork to a private repository when you require a secure copy of a project where contributions are not publicly shared, yet you still need to stay in sync with upstream changes.

Does syncing a private GitHub fork require special authentication?

Yes, syncing a private GitHub fork requires authentication to access and fetch new commits from the upstream parent repository securely, ensuring only authorized users can pull updates into the private copy.