pb-open-source
Prepare a project for open sourcing: a sanitized fork with secrets and internal references stripped, a sanitizer verdict, README and LICENSE, then a new PRIVATE GitHub repo created and pushed only aft
SKILL.mdskills/playbooks/pb-open-source/SKILL.md
GitHubSanitized fork in a new private repo
What you get: a sanitized copy of the project with README and LICENSE in a new private GitHub repo, with the sanitizer verdict logged. Going public stays your own action, outside this run.
Inputs
- source_repo — the local checkout to fork, asked if missing
- target_name — the new repo name, asked if missing
- owner — the GitHub user or org for the new repo, asked if missing
- license — the license id for the LICENSE file (for example MIT or Apache-2.0), asked if missing
Steps
- opensource-forker (agent) — source_repo → fork dir
<scratch>/<target_name>(<scratch>=mktemp -d) and.env.example, secrets and internal references stripped, git history cleaned — fork dir exists; the source repo is untouched (git -C <source_repo> status --shortis unchanged) - opensource-sanitizer (agent) — fork dir → report with the verdict PASS, FAIL or PASS-WITH-WARNINGS in the run log — FAIL stops the run: the findings are logged, nothing is created or pushed
- github-repo + readme — fork dir, license → README.md and LICENSE in the fork dir following the repo standards — stops for approval (the human reads both files and the warnings from step 2)
- git —
git -C <fork dir> rev-parse --git-dir(not a repo →git -C <fork dir> init), thengit -C <fork dir> add README.md LICENSEplus each file the forker produced, listed by explicit path (never-Aor.), thengit -C <fork dir> commit -m "Initial sanitized release"→ commit SHA in the run log —git -C <fork dir> status --shortis empty and README.md and LICENSE are ingit -C <fork dir> ls-tree -r HEAD --name-only - [GO] gh repo create —
gh repo create <owner>/<target_name> --private— the WAITING FOR GO line names owner, name and--private. The run stops here until the human types GO. (gh repo createis not hooked; this GO is its only guard.) - github —
gh repo view <owner>/<target_name> --json visibility -q .visibility→ run log line — equalsPRIVATE, else stop - [GO] git push —
git -C <fork dir> remote add origin <url>is part of this step, then the push of the default branch toorigin— the WAITING FOR GO line names the remote URL, the branch and the commit SHA from step 4. The run stops here until the human types GO. (Where the hook runs, it coversgit push; the other commands here are not hooked, so this GO is their only guard.) - github —
gh repo view <owner>/<target_name> --json visibility -q .visibility, thengh api repos/<owner>/<target_name>/contents/LICENSEand.../contents/README.md→ final run log line — LICENSE and README.md both return 200 on the default branch, else stop; the run log ends with the sanitizer verdict and the line "visibility stays PRIVATE; flipping it is the human's own action"
Run log: production_artifacts/pb-open-source-<date>.md in the start directory, never committed
Rules
- This playbook never runs
gh repo edit --visibilityor any other command that changes visibility. - Anything other than the literal GO (case-insensitive) is not a GO; a GO covers only that one step, one time.
- GO is by contract in every harness. The go-gate hook is only a backstop on Claude Code, OpenCode and agy (Codex: unverified; Cursor, Kimi: none). A missing hook is never permission to proceed.
- A failed check stops the run: write the failure into the run log and report. No silent retries.
- Write one run-log line per step as it completes (
N. done|skipped|failed — artifact — check result) andWAITING FOR GO: <step>at each gate.