flip-public

Validates and executes the one-way flip of a private GitHub repository to public visibility.

Updated May 12, 2026
One-click install
npx skills add https://github.com/fryanpan/ai-team-lead --skill flip-public-fryanpan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flip-public
Source: https://github.com/fryanpan/ai-team-lead/tree/main/plugin/team-lead-fleet/skills/flip-public
Command: npx skills add https://github.com/fryanpan/ai-team-lead --skill flip-public-fryanpan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Flipping a private GitHub repo to public is irreversible — full commit history, PR descriptions, and closed issues all become permanently visible and indexed. This Skill enforces a pre-flip checklist so credentials, internal URLs, real names, and missing licenses or onboarding docs don't leak into the public record. ## Core Features & Use Cases - Pre-flip checklist: Verifies a /setup skill exists, a LICENSE file is present (defaulting to MIT), and the README follows a clone → claude → /setup onboarding pattern. - Two-layer scrubbing: Runs regex-based and Haiku-based scrub scripts over tracked files, plus manual review of commit history, PR descriptions, and closed issues, with squash or git filter-repo options for dirty history. - Security and protection pass: Greps for hardcoded credentials and internal network references, then applies branch protection on main (required PR reviews, enforce_admins, push restrictions) immediately after the visibility flip. - Use Case: Before launching a side project, you ask to go public — the Skill walks each checklist item, scrubs a leaked internal hostname from history, adds an MIT license, flips visibility with gh repo edit, and confirms the result in an incognito browser. ## Quick Start Ask the assistant to run the flip-public checklist and make this repository public on GitHub.

Frequently Asked Questions about flip-public

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

FAQPage Schema
How do I safely make a private GitHub repo public?▼

Run a pre-flip checklist: confirm a LICENSE and onboarding README exist, scrub tracked files and full commit history for secrets and internal references, then flip visibility with gh repo edit --visibility public and immediately apply branch protection on main.

How do I remove secrets from git history before going public?▼

Squash dirty history to a single initial commit with git reset --soft, or rewrite content across history with git filter-repo while preserving dates. Choose based on whether the dated history itself has evidentiary value, such as prior-art claims.

What becomes visible when a GitHub repo is flipped public?▼

The entire commit history, all PR descriptions and comments, and closed issues become publicly visible and indexed. Making the repo private again does not undo forks, clones, or search engine indexing.

Does branch protection work on free personal GitHub accounts?▼

PR review requirements and enforce_admins work via the classic protection API on personal repos, but push restrictions may be silently ignored on the free tier. Use GitHub Rulesets in the repository settings to restrict who can push.

When should I not flip a repository public?▼

Do not flip when you only need to share a single file or branch, when scrubbing has not run, or when a multi-author repo's contributors have not consented. Public commit attribution and history are permanent.