split-portfolio

Migrate ApexYard adopters from a public fork to a split-portfolio layout with private sibling repo.

489|254|Updated Apr 5, 2026

Search Tags:#git #portfolio #history rewrite #github migration #fork visibility #issue redaction #sdlc automation

Ready to run

npx skills add https://github.com/me2resh/apexyard --skill split-portfolio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: split-portfolio
Source: https://github.com/me2resh/apexyard/tree/main/.claude/skills/split-portfolio
Command: npx skills add https://github.com/me2resh/apexyard --skill split-portfolio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of getting stuck after you publish a fork publicly and GitHub Free prevents changing fork visibility, leaving private project names exposed or unusable for the intended multi-project workflow.

Core Features & Use Cases

Guided destructive migration: Moves the registry and project docs into a newly created private sibling repo while rewriting the public fork history to remove private layout artifacts.
Operator-confirmation safety gates: Enforces explicit confirmation before irreversible steps like history rewrite and force-push, and blocks unsafe reruns via drift detection.
State-safe recovery options: Creates a backup-pre-rewrite branch for a 7-day recovery window and supports read-only inspection via --verify and planning via --dry-run.
Redaction of exposed issue/PR content: Redacts bodies that mention registered project names and surfaces the timeline-API caveat so operators know what persists.

Quick Start

Run split-portfolio migration in check mode first by executing: /split-portfolio --verify

Frequently Asked Questions about split-portfolio

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

FAQPage Schema

How do I change a public GitHub fork to private when visibility cannot be changed on Free?▼

To resolve the GitHub Free fork visibility lock, migrate to a split-portfolio layout by creating a private sibling repo for your framework while rewriting the public fork history to remove private artifacts.

How does git history rewrite remove private project names from a public repository?▼

Git history rewrite removes private project names by rewriting the public fork commits to strip private layout artifacts, requiring explicit operator confirmation before executing the irreversible force-push.

Can I preview a repository migration before applying destructive history changes?▼

You can preview the repository migration by running the process in read-only inspection mode using the verify flag, or simulate the execution plan without changes using the dry-run flag.

What happens to exposed GitHub issues and pull requests after rewriting repository history?▼

Exposed GitHub issue and PR bodies mentioning registered project names are redacted, but operators must note the timeline-API caveat where certain historical data persists despite the rewrite.

Is there a recovery window if a force-push removes needed commits during a portfolio split?▼

A backup-pre-rewrite branch is created automatically to provide a 7-day recovery window, while drift detection blocks unsafe reruns to ensure state-safe migration execution.