Opensource Pipeline

Automates the nerve-wracking process of taking a private project public by running it through a three-stage pipeline: fork and strip secrets, verify nothing leaked, then generate all the open-source boilerplate (CLAUDE.md, setup.sh, README, license, contribution guidelines). The sanitizer agent is the real safety net here, running six scan categories and blocking publication on critical findings like exposed credentials or PII. Everything stages to a review directory before you push anything to GitHub. Honestly most useful if you've got internal tooling you want to share but dread the manual scrubbing. The full pipeline probably saves an hour of paranoid grepping and template copying.

skills.sh installs: 3.7K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill opensource-pipeline --agent claude-code

Installs into .claude/skills of the current project.

Files

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.

SKILL.md on GitHub