opensource-pipeline

原文涵盖的主题

• Open-Source Pipeline Skill
• When to Activate
• Commands
• Protocol
• /opensource fork PROJECT
• Step 1: Gather Parameters
• Step 2: Create Staging Directory
• Step 3: Run Forker Agent

Safely open-source any project through a 3-stage pipeline: Fork (strip secrets) → Sanitize (verify clean) → Package (CLAUDE.md + setup.sh + README). 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 | 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 | Full pipeline — the main workflow. 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. "Descriptio

这里只展示节选，请以完整原文和当前要求为准。