Agent skill · creative production · affaan-m
opensource-pipeline
Open-source pipeline: fork, sanitize, and package private projects for safe public release. Chains 3 agents (forker, sanitizer, packager). Triggers: '/opensource', 'open source this', 'make this public', 'prepare for open source'. Use when a private project must be forked, stripped of secrets, and packaged for public release.
Why this skill is useful
Adds a complete executable pipeline for safely open-sourcing projects, including forking, sanitizing, and packaging scripts that aren't commonly available.
What it needs
Requires gh installed locally. About 7k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
Open-Source Pipeline Skill Safely open-source any project through a 3-stage pipeline: Fork (strip secrets) → Sanitize (verify clean) → Package (CLAUDE.md + setup.sh + README). When to Activate User says "open source this project" or "make this public" User wants to prepare a private repo for public release User needs to strip secrets before pushing to GitHub User invokes /opensource fork, /opensource verify, or /opensource package Commands Command Action --------- -------- /opensource fork PROJECT Full pipeline: fork + sanitize + package /opensource verify PROJECT Run sanitizer on existing repo /opensource package PROJECT Generate CLAUDE.md + setup.sh + README /opensource list Show all staged projects /opensource status PROJECT Show reports for a staged project Protocol /opensource fork PROJECT Full pipeline — the main workflow. Step 1: Gather Parameters Resolve the project path. If PROJECT contains /, treat as a path (absolute or relative). Otherwise check: current working directory, $HOME/PROJECT, then ask the user. Ask the user: 1. "Which project?" (if not found) 2. "License? (MIT / Apache-2.0 / GPL-3.0 / BSD-3-Clause)" 3. "GitHub org or username?" (default: detect via gh api user -q .login) 4. "GitHub repo name?" (default: project name) 5. "Description for README?" (analyze project for suggestion) Step 2: Create Staging Directory Step 3: Run Forker Agent Spawn the opensource-forker agent: Wait for completion. Read {STAGINGPATH}/FORKREPORT.md. The forker's single commit is only the starting point: gh repo create --push (Step 7) publishes commits, not the working tree. Every later change (sanitizer fixes, packager output) must be folded into that commit, so the public history is one commit that matches the tree the sanitizer passed. The reports stay out of it. Fold changes in with: An amend leaves a secret that was removed from a file out of the new commit. A new commit on top would publish it in history. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/opensource-pipeline--fc2faa