Fork, sanitize, and package private projects for safe open-source release.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "opensource-pipeline" skill from askskill: 1. Download https://raw.githubusercontent.com/affaan-m/ECC/main/skills/opensource-pipeline/SKILL.md 2. Save it as ~/.claude/skills/opensource-pipeline/SKILL.md 3. Reload skills and tell me it's ready
Please open-source this private project: create a public-safe fork, remove secrets, internal domains, proprietary configs, and sensitive docs, then prepare the README, license, and release package, and give me a public release checklist.
A sanitized, packaged open-source release version with a checklist of risks and follow-ups.
Open source this repository, focusing on environment variables, API keys, company names, internal links, and sensitive comments; keep the reusable code and generate a GitHub-ready public project structure.
A public-hosting-ready repository structure plus a summary of detected and handled sensitive items.
Make this public. Turn the current private project into a releasable open-source package: fork it, sanitize it, complete the documentation, add an open-source license, and note which files should not be public.
A ready-to-publish open-source project package with docs, license, and notes on excluded files.
Safely open-source any project through a 3-stage pipeline: Fork (strip secrets) → Sanitize (verify clean) → Package (CLAUDE.md + setup.sh + README).
/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.
SOURCE_PATH="<resolved absolute path>"
STAGING_PATH="$HOME/opensource-staging/${PROJECT_NAME}"
Ask the user:
gh api user -q .login)mkdir -p $HOME/opensource-staging/
Spawn the opensource-forker agent:
Agent(
description="Fork {PROJECT} for open-source",
subagent_type="opensource-forker",
prompt="""
Fork project for open-source release.
Source: {SOURCE_PATH}
Target: {STAGING_PATH}
License: {chosen_license}
Follow the full forking protocol:
1. Copy files (exclude .git, node_modules, __pycache__, .venv)
2. Strip all secrets and credentials
3. Replace internal references with placeholders
4. Generate .env.example
5. Clean git history
6. Generate FORK_REPORT.md in {STAGING_PATH}/FORK_REPORT.md
"""
)
Wait for completion. Read {STAGING_PATH}/FORK_REPORT.md.
Spawn the opensource-sanitizer agent:
Agent(
description="Verify {PROJECT} sanitization",
subagent_type="opensource-sanitizer",
prompt="""
Verify sanitization of open-source fork.
Project: {STAGING_PATH}
Source (for reference): {SOURCE_PATH}
Run ALL scan categories:
1. Secrets scan (CRITICAL)
2. PII scan (CRITICAL)
3. Internal references scan (CRITICAL)
4. Dangerous files check (CRITICAL)
5. Configuration completeness (WARNING)
6. Git history audit
Generate SANITIZATION_REPORT.md inside {STAGING_PATH}/ with PASS/FAIL verdict.
"""
)
Wait for completion. Read {STAGING_PATH}/SANITIZATION_REPORT.md.
If FAIL: Show findings to user. Ask: "Fix these and re-scan, or abort?"
If PASS or PASS WITH WARNINGS: Continue to Step 5.
Spawn the opensource-packager agent:
Agent(
description="Package {PROJECT} for open-source",
subagent_type="opensource-packager",
prompt="""
Generate open-source packaging for project.
Project: {STAGING_PATH}
License: {chosen_license}
Project name: {PROJECT_NAME}
Description: {description}
GitHub repo: {github_repo}
Generate:
1. CLAUDE.md (commands, architecture, key files)
2. setup.sh (one-command bootstrap, make executable)
3. README.md (or enhance existing)
4. LICENSE
5. CONTRIBUTING.md
6. .github/ISSUE_TEMPLATE/ (bug_report.md, feature_request.md)
"""
)
Present to user:
Open-Source Fork Ready: {PROJECT_NAME}
Location: {STAGING_PATH}
License: {license}
…
Handle returns, refunds, fraud checks, and warranty claim decisions efficiently.
Use Bun for runtime, bundling, testing, packages, and Node migration decisions.
Use the correct Ethereum Keccak-256 hashing in Node.js and TypeScript.
Apply Nuxt 4 patterns for SSR safety, performance, and data fetching.
Generate images, videos, and audio with one unified AI media workflow.
Design Quarkus 3 backend patterns for messaging, APIs, data, and async workflows.
Build, run, and manage workflows with an open-source agent operating system.
Coordinate GitHub and Linear workflows for triage, tracking, and execution alignment.
Deploy any local folder to a live URL in one command.
Fetch GitHub issues, create fixes, open PRs, and handle reviews.
Monitor main branch updates and safely sync your branch with AI-assisted conflict handling.
Assess open-source health, dependency risks, trends, and license differences.