Split Portfolio

Writing rule

When this skill writes a durable artifact, read .claude/rules/writing-standard.md. Use the controlled technical writing profile.

/split-portfolio — Migrate to split-portfolio mode

Automates the recovery flow for ApexYard adopters who hit the trip-wire documented in docs/multi-project.md — pushed private project names to a public fork, then realized GitHub Free disallows fork-visibility changes.

The skill is destructive: it force-pushes the public fork's main branch after rewriting history, redacts GitHub Issue / PR body content, and creates a new private repo. Every destructive step has an explicit operator-confirmation gate. None of those gates are skip-able.

Path resolution

Read the registry path via portfolio_registry, the per-project docs dir via portfolio_projects_dir, and the ideas backlog via portfolio_ideas_backlog — all from .claude/hooks/_lib-portfolio-paths.sh. Source the helper at the top of any bash block that touches those paths:

source "$(git rev-parse --show-toplevel)/.claude/hooks/_lib-read-config.sh"
source "$(git rev-parse --show-toplevel)/.claude/hooks/_lib-portfolio-paths.sh"
registry=$(portfolio_registry)

Defaults match today's single-fork layout (./apexyard.projects.yaml, ./projects, ./projects/ideas-backlog.md). Adopters in split-portfolio mode override the portfolio.{registry, projects_dir, ideas_backlog} keys in .claude/project-config.json. Don't hardcode literal apexyard.projects.yaml or projects/ paths in bash blocks — the helper resolves whichever mode the adopter is in. See docs/multi-project.md.

Modes

Pre-flight refusals (before doing anything)

The skill refuses with a clear redirect when:

Refusal at any of these gates is silent on every other check — show only the relevant message.

Process

0. Mark this session as bootstrap (REQUIRED for non---verify modes)

/split-portfolio rewrites fork-root files (.gitignore, .claude/project-config.json, registry symlinks) which the require-active-ticket.sh PreToolUse hook would block — and the whole point of the migration is that the fork's existing private project names should no longer be referenced, so even filing a placeholder ticket is awkward. Write a marker so the hook exempts this skill (it's on the default bootstrap_skills list in .claude/project-config.defaults.json):

# Only on full / --dry-run modes. --verify is read-only and doesn't need the marker.
mkdir -p .claude/session && echo "split-portfolio" > .claude/session/active-bootstrap

Clear the marker at the end of the migration (or on a confirmed-abort). If the skill is interrupted mid-flow, the SessionStart hook clear-bootstrap-marker.sh clears it at the start of the next session. See AgDR-0011 + me2resh/apexyard#150.

--verify mode (no destructive ops, safe to run anytime)

1. Source _lib-read-config.sh and _lib-portfolio-paths.sh.
2. Run portfolio_validate. Capture result.
3. Detect mode: config-block (presence of portfolio: block in .claude/project-config.json) vs symlink (test -L apexyard.projects.yaml) vs single-fork (neither).
4. List backup-pre-rewrite branch age, if present (gh api repos/<fork>/branches/backup-pre-rewrite --jq .commit.commit.author.date).
5. Detect drift (config-block AND symlink both present pointing at different things — broken state).
6. Print a structured report:

/split-portfolio --verify

Mode:                config-block (recommended) | symlink (legacy) | single-fork | mixed (DRIFT)
Registry resolves:   /abs/path/apexyard.projects.yaml
                     [exists | MISSING]
Projects dir:        /abs/path/projects
                     [exists | MISSING]
Ideas backlog:       /abs/path/projects/ideas-backlog.md
                     [exists | creatable | MISSING parent]
Validate:            OK | broken: <reason>

backup-pre-rewrite:  age=12d (consider deleting after 7-day soak)
                     OR not present

Drift:               none | YES — config and symlink point at different paths

Exit 0 if valid + no drift; exit 1 if validate fails or drift detected.

Full migration (10 steps)

Step 1 — Pre-flight checklist

After the pre-flight refusals above pass, show the operator a checklist and ask for explicit confirmation:

About to migrate this fork to split-portfolio mode. Destructive operations will follow.

Changes you will see:
  - A new private repo created at <suggested-name>
  - This fork's git history rewritten to remove apexyard.projects.yaml + projects/
  - This fork's main branch force-pushed
  - GitHub Issue / PR bodies on this fork that named registered projects redacted
  - .claude/project-config.json updated with a `portfolio:` block pointing at the sibling
  - onboarding.yaml COPIED to the sibling (canonical) + untracked from the public fork
  - workspace/<name>/ contents MOVED to the sibling (gigabytes — no point doubling disk)
  - .apexyard-fork marker written + v2 portfolio keys added (split-portfolio v2 layout)

Reversibility:
  - A backup-pre-rewrite branch is pushed before any rewrite (recoverable for 7 days)
  - Force-push is irreversible at the GitHub level for anyone who cloned in the last hour
  - GitHub Issue/PR edit history (timeline API) survives — full purge requires repo deletion

Have you read docs/multi-project.md § "Migrating from single-fork to split-portfolio"? (y/n)
Are you running this during a low-traffic window so other clones won't be surprised? (y/n)

Continue? (yes / cancel)

Step 2 — Snapshot extraction

Copy the registry + projects/ to a tmpdir. This is the data that will be pushed to the new private repo. Run BEFORE any destructive operation so a failure here doesn't cost the operator anything.

SNAPSHOT=$(mktemp -d)
cp "$(portfolio_registry)" "$SNAPSHOT/"
cp -r "$(portfolio_projects_dir)" "$SNAPSHOT/"
echo "Snapshot at: $SNAPSHOT"

Confirm to operator: snapshot exists, file count matches expectation. If not, refuse.

Step 3 — Create the private repo

The suggested default name is <account>/<fork>-portfolio — keeps the relationship to the public fork explicit on GitHub. Compute <fork> from the public-fork repo name (gh repo view --json name -q .name) so the suggestion is correct even when the fork was renamed (e.g. fork = cos → suggested portfolio = cos-portfolio).

Suggested name: <account>/<fork>-portfolio    (e.g. <account>/apexyard-portfolio)
Override? (Enter to accept default, or type a different name)
> _

Creating private repo... gh repo create <name> --private --description "ApexYard private portfolio: registry + per-project handover docs"
Continue? (yes / cancel)

If the repo name already exists in the operator's account, refuse and ask for a different name.

Step 4 — Push the snapshot to the private repo

cd "$SNAPSHOT"
git init -q
git checkout -b main
git add apexyard.projects.yaml projects/
git commit -q -m "chore: import portfolio snapshot from public fork"
gh repo set-default <name>
git remote add origin "https://github.com/<account>/<name>.git"
git push -u origin main

Print: ✓ Private portfolio repo populated at <name>.

Step 4a — Configure branch protection on the private portfolio repo

Immediately after the snapshot push, apply branch protection to main on the new private repo so that no one (including the operator's own account) can push directly to main without a PR.

The protection is intentionally lenient: no required status checks (CI may not exist yet on a brand-new private repo), enforce_admins: false so the operator can still merge an admin PR when needed, and one required approving review.

OWNER=$(gh api user --jq .login)
REPO_NAME=<private-repo-name>   # resolved from step 3

gh api -X PUT "repos/${OWNER}/${REPO_NAME}/branches/main/protection" \
  --input - <<'EOF'
{
  "required_status_checks": null,
  "enforce_admins": false,
  "required_pull_request_reviews": {
    "required_approving_review_count": 1,
    "dismiss_stale_reviews": false
  },
  "restrictions": null
}
EOF

The gh api call requires the operator to have admin permission on the new private repo. Because the skill itself just created the repo via gh repo create, the operator is always the repo owner and therefore has admin access — so this call should succeed in the normal flow.

However, if the repo was pre-created by an org admin and the operator only has write access, the PUT will return HTTP 403. Handle this gracefully:

if ! gh api -X PUT "repos/${OWNER}/${REPO_NAME}/branches/main/protection" \
     --input - <<'EOF'
{
  "required_status_checks": null,
  "enforce_admins": false,
  "required_pull_request_reviews": {
    "required_approving_review_count": 1,
    "dismiss_stale_reviews": false
  },
  "restrictions": null
}
EOF
then
  echo ""
  echo "⚠  Branch protection could not be applied to ${OWNER}/${REPO_NAME}/branches/main."
  echo "   You do not have admin access to that repo, or it is under an org with"
  echo "   restricted branch-protection APIs."
  echo "   Apply protection manually: GitHub → ${OWNER}/${REPO_NAME} → Settings → Branches → Add rule"
  echo "   Recommended rule: require PR with 1 approval, no bypass for admins off."
  echo "   Continuing migration — branch protection is advisory at this stage."
fi

Idempotency: if branch protection is already configured (re-run scenario), the PUT is a no-op update and is safe to call again.

On success, print:

✓ Branch protection configured on ${OWNER}/${REPO_NAME}:main
    require_pull_request_reviews: 1 approval required
    required_status_checks:       none (add when CI is in place)
    enforce_admins:               false

Step 5 — Backup branch on the public fork

Before any rewrite. Recoverable safety net.

cd /path/to/public/fork
git fetch origin
git push origin "origin/main:refs/heads/backup-pre-rewrite"

Print: ✓ backup-pre-rewrite pushed (will be auto-cleaned after 7-day soak in step 10).

Step 6 — History rewrite

Detect: was the registry + projects/ added in a single commit? If yes, the cheap path:

PARENT=$(git log --format=%H --all -- apexyard.projects.yaml | tail -n 1)^
git reset --hard "$PARENT"

Otherwise, use git filter-repo (recommends installing if missing):

if ! command -v git-filter-repo >/dev/null 2>&1; then
  echo "git-filter-repo not installed. Install it (e.g. brew install git-filter-repo) and re-run."
  exit 1
fi
git filter-repo --path apexyard.projects.yaml --path projects --invert-paths

After rewrite, show the operator the diff: how many commits changed, sample of removed paths.

Step 7 — Force-push to fork's main

This is the irreversible step. Single explicit confirmation gate:

About to force-push the rewritten main to <account>/<fork>.

This is irreversible at GitHub for anyone who cloned in the last hour.
Continue? (yes / cancel)

git push --force-with-lease origin main

If the lease check fails (someone else pushed since the operator last fetched), refuse — operator should investigate before re-running.

Step 8 — Redact GitHub Issue / PR bodies

For each registered project name, search the public fork's issues + PRs for bodies that mention them:

source "$(git rev-parse --show-toplevel)/.claude/hooks/_lib-read-config.sh"
source "$(git rev-parse --show-toplevel)/.claude/hooks/_lib-portfolio-paths.sh"
REGISTRY=$(portfolio_registry)

# Read names from snapshot (still has the registry)
names=$(yq eval '.projects[].name' "$SNAPSHOT/apexyard.projects.yaml")

for name in $names; do
  # Issues + PRs mentioning the name in body
  matching=$(gh issue list --repo <fork> --search "$name in:body" --json number,title,body --limit 100)
  matching_prs=$(gh pr list --repo <fork> --search "$name in:body" --json number,title,body --limit 100)

  for item in $matching $matching_prs; do
    # Show diff to operator: what was named, what redaction we'll apply
    # Confirm per item before writing
    # gh issue edit <n> --repo <fork> --body-file <redacted>
    # OR gh pr edit <n> --repo <fork> --body-file <redacted>
  done
done

After the loop, explicitly print the timeline-API caveat:

⚠ Edit history survives.

GitHub's timeline API still has the original body content. Full purge of
the original text requires deleting and recreating the repo (which loses
issue numbers + PR numbers + history). The redaction above hides the
content from casual viewers, search engines, and the GitHub UI default
view — that's it.

Step 9 — Write the portfolio: config block + .gitignore

# .gitignore additions in the public fork
cat >> .gitignore <<'EOF'

# Portfolio data lives in a separate private repo (split-portfolio mode).
# See docs/multi-project.md.
apexyard.projects.yaml
projects
EOF

# Untrack any framework projects/README.md from upstream (it'll be replaced by the private sibling's content)
git rm --cached -r projects 2>/dev/null || true

# Write portfolio: block to project-config (v2 keys added in Steps 9a–9d below)
PRIVATE_REPO_REL="../<private-repo-name>"
cat > .claude/project-config.json <<JSON
{
  "portfolio": {
    "registry": "$PRIVATE_REPO_REL/apexyard.projects.yaml",
    "projects_dir": "$PRIVATE_REPO_REL/projects",
    "ideas_backlog": "$PRIVATE_REPO_REL/projects/ideas-backlog.md"
  }
}
JSON

# NOTE (me2resh/apexyard#1031): .claude/project-config.json is deliberately
# NOT staged. It is gitignored and untracked upstream, so `git add` on it
# exits 1 — git still stages the other paths, but the non-zero exit stops
# this step and the commit below never runs. It is also the wrong file to
# commit here: the block just written names the PRIVATE sibling repo's path,
# and this ops fork may be public. Never `git add -f` it — that restores the
# tracked copy whose overwrite-on-checkout is the data loss #1031 fixed.
git add .gitignore
git commit -m "chore: configure split-portfolio mode (#143 / #145)"

If .claude/project-config.json already has a non-portfolio block, merge rather than overwrite — preserve existing keys.

If it has a portfolio: block already, refuse and ask the operator to manually reconcile.

Step 9a — Produce the v2 layout (onboarding.yaml + workspace + marker + v2 config keys)

Steps 9a–9d extend the migration so the final fork is split-portfolio v2, not v1. Without these, adopters would land on the v1 layout and need a follow-up /update to migrate again. See AgDR-0021 § "v1→v2 migration semantics" for the copy-vs-move rationale per file class.

Resolve the sibling repo dir from the existing portfolio.registry path (the parent dir of the registry file is the sibling repo root):

SIBLING_ROOT=$(dirname "$(jq -r '.portfolio.registry' .claude/project-config.json)")
# e.g. SIBLING_ROOT=../<private-repo-name>

Per-file-class confirmation — ask separately so the operator can defer either:

Copy onboarding.yaml to sibling private repo? [Y/n]
Move workspace/<name>/ contents to sibling private repo? [Y/n]   # surfaces disk size: du -sh workspace

onboarding.yaml is copied (not moved): the file is small, the legacy tracker fallback at _lib-ops-root.sh still reads it as part of the legacy ops-root walk-up, and keeping a snapshot in the public fork is a safety net while the sibling-repo copy becomes the canonical source of truth. workspace/<name>/ is moved: clones are gigabytes; doubling disk makes no sense.

Copy onboarding.yaml (not move — see AgDR-0021 § H)

if [ -f onboarding.yaml ] && [ ! -f "$SIBLING_ROOT/onboarding.yaml" ]; then
  # COPY (cp -p preserves mtimes/permissions). Sibling becomes canonical;
  # public-fork copy is left as a snapshot and untracked below.
  cp -p onboarding.yaml "$SIBLING_ROOT/onboarding.yaml"
  ( cd "$SIBLING_ROOT" && git add onboarding.yaml )

  # Untrack from the public fork so future commits don't ship it. The file
  # is left on disk (gitignored by Step 9c) as a legacy-tool snapshot.
  git rm --cached onboarding.yaml 2>/dev/null || true
elif [ -f "$SIBLING_ROOT/onboarding.yaml" ] && [ -f onboarding.yaml ]; then
  # Both present — surface and stop; operator reconciles.
  printf 'WARNING: onboarding.yaml exists in BOTH the public fork and the sibling repo.\n' >&2
  printf '  Reconcile manually (the sibling-repo copy is canonical) before re-running.\n' >&2
  exit 1
fi

Idempotence: if onboarding.yaml is already only in the sibling repo (and untracked in the public fork), this block is a no-op.

Step 9b — Move workspace// contents to the sibling

if [ -d workspace ] && [ "$(ls -A workspace 2>/dev/null)" ]; then
  mkdir -p "$SIBLING_ROOT/workspace"
  for entry in workspace/*; do
    [ -e "$entry" ] || continue
    name=$(basename "$entry")
    # workspace/README.md is a framework artefact explaining the convention —
    # it stays in the public fork. See AgDR-0021 § G.
    if [ "$name" = "README.md" ]; then
      continue
    fi
    if [ -e "$SIBLING_ROOT/workspace/$name" ]; then
      echo "WARNING: workspace/$name exists in BOTH locations — skipped."
      continue
    fi
    mv "$entry" "$SIBLING_ROOT/workspace/$name"
  done
fi

Idempotence: empty workspace/ (no entries to move, or only README.md left) is a no-op.

Step 9c — Extend .gitignore for v2 file classes

NEEDS=()
grep -qxF onboarding.yaml .gitignore 2>/dev/null || NEEDS+=(onboarding.yaml)
grep -qxF 'workspace/*' .gitignore 2>/dev/null || NEEDS+=('workspace/*')
grep -qxF '!workspace/README.md' .gitignore 2>/dev/null || NEEDS+=('!workspace/README.md')

if [ "${#NEEDS[@]}" -gt 0 ]; then
  {
    echo ""
    echo "# Split-portfolio v2 (framework ≥ #242): onboarding + workspace entries live in the private sibling repo."
    for n in "${NEEDS[@]}"; do echo "$n"; done
  } >> .gitignore
  git add .gitignore
fi

Step 9d — Write the .apexyard-fork marker + v2 config-block keys

The marker is presence-only: readers (every ops-root walk) MUST ignore content; only file presence matters. Writers MAY include a single explanatory line so head .apexyard-fork is informative — both echo "# comment" > .apexyard-fork and touch .apexyard-fork are valid. See AgDR-0021 § B.

if [ ! -f .apexyard-fork ]; then
  echo "# This file marks the directory as an ApexYard ops fork (split-portfolio v2)." > .apexyard-fork
  git add .apexyard-fork
fi

Add the four v2 keys to .claude/project-config.json — onboarding, workspace_dir, custom_skills_dir, custom_handbooks_dir. Use jq to merge so existing keys (Step 9's registry / projects_dir / ideas_backlog) are preserved, and // $x short-circuits if the operator already added a key by hand:

PCONFIG=.claude/project-config.json
TMP=$(mktemp)
jq --arg onb "$SIBLING_ROOT/onboarding.yaml" \
   --arg ws  "$SIBLING_ROOT/workspace" \
   --arg cs  "$SIBLING_ROOT/custom-skills" \
   --arg ch  "$SIBLING_ROOT/custom-handbooks" \
   '.portfolio.onboarding         = (.portfolio.onboarding         // $onb)
    | .portfolio.workspace_dir    = (.portfolio.workspace_dir    // $ws)
    | .portfolio.custom_skills_dir    = (.portfolio.custom_skills_dir    // $cs)
    | .portfolio.custom_handbooks_dir = (.portfolio.custom_handbooks_dir // $ch)' \
   "$PCONFIG" > "$TMP" && mv "$TMP" "$PCONFIG"
git add "$PCONFIG"

Idempotence: re-running 9d is a no-op (existing key values are preserved via // $x; the marker write skips when present).

Step 10 — Verify + cleanup

Verify migration:

source .claude/hooks/_lib-read-config.sh
source .claude/hooks/_lib-portfolio-paths.sh
if ! portfolio_validate; then
  echo "Migration produced a broken config — see error above. NOT proceeding to cleanup."
  exit 1
fi

# Confirm public fork's main no longer has the registry
git ls-tree --name-only HEAD apexyard.projects.yaml && {
  echo "ERROR: registry still in main. Force-push didn't take effect?"
  exit 1
}

Cleanup (opt-in, default-no):

backup-pre-rewrite branch holds your pre-migration history. Default: keep for 7-day soak.

Delete it now? (y/N)

If y: gh api -X DELETE repos/<fork>/git/refs/heads/backup-pre-rewrite.

Final report:

✓ Split-portfolio migration complete.

  Public fork:        <account>/<fork>      (registry removed, history rewritten)
  Private portfolio:  <account>/<private>   (registry + projects/ pushed)
  Branch protection:  <account>/<private>:main (1 required review, no required status checks)
  Config block:       .claude/project-config.json (portfolio.* set)
  Backup branch:      backup-pre-rewrite (kept for 7 days, run /split-portfolio --verify to monitor)

  Bodies redacted:    <N> issues, <M> PRs (timeline API survives — see warning above)

  Next step:          commit + push the new .gitignore + project-config.json:
                        git push origin main

Idempotency

Re-running the skill on a partially-migrated fork picks up where it left off:

The --dry-run flag walks through every step printing the commands but executes none. Useful for the operator to preview the destructive ops before running real.

Cleanup (REQUIRED before exit)

rm -f .claude/session/active-bootstrap

Run on every exit path (successful migration, confirmed abort, refusal-in-flight). If the skill is interrupted before this step, clear-bootstrap-marker.sh clears the stale marker on the next session.

Rules

1. No destructive op without an explicit operator-typed yes. Single-character y is acceptable; ambiguous ok / sure is not.
2. No --force-by-default. Force-push uses --force-with-lease; if the lease fails, refuse.
3. Never delete backup-pre-rewrite automatically. Even at step 10, deletion is opt-in. Default: keep for 7 days.
4. Surface the timeline-API caveat verbatim at step 8. Adopters must see it. No abstraction.
5. Refuse on already-migrated. Detection covers config-block mode, symlink mode, and mixed-drift. Re-run with --verify is fine; full re-run requires manual cleanup first.
6. Resolve paths via the helper. Step 8 + step 9 + step 10 all use portfolio_registry, portfolio_projects_dir, portfolio_validate from _lib-portfolio-paths.sh. No literal apexyard.projects.yaml references in bash blocks (the snapshot's path is passed as a separate variable).

Part of ApexYard — multi-project SDLC framework for Claude Code · MIT.