What does this skill do?

The Open Source Skill Pipeline automates the preparation of private repositories for public release on GitHub. It runs a three-phase pipeline—fork, sanitization, and packaging—that removes secrets and credentials, generates standard documentation (README, CONTRIBUTING, setup.sh), and verifies that the code is secure before publishing it.

Safe Fork
Copy the project—excluding .git, node_modules, and other artifacts—to an isolated staging directory.
Cleansing Secrets
Scan the code for credentials, PII, and internal references, generating a PASS or FAIL report.
Open Source Packaging
It automatically generates README.md, LICENSE, CONTRIBUTING.md, setup.sh, and issue templates.
Pre-Publication Review
Run the sanitizer on a project that has already been forked to confirm that there are no leaks before pushing it.

Usage examples

🔄 Complete pipeline
/opensource fork mi-app-node — prepare this private project for release on GitHub under the MIT license.
🔒 Verification only
/opensource verify mi-app-node — checks whether there are any secrets or credentials left in the forked project.
📦 Pack documentation
Generate the README.md, CONTRIBUTING.md, and setup.sh files for my project before publishing it on GitHub.
✅ Final review
Check the staging directory for mi-app-node and let me know if it's safe to create the public repository.

Features

Three-phase pipeline Automatically chained branching, cleanup, and packaging with confirmation at each stage.
Detection of Secrets and PII In-depth scanning for credentials, sensitive environment variables, and personally identifiable information.
Generating .env.example Automatically create a template of environment variables without sensitive values.
Complete open-source documentation Generates README.md, LICENSE, CONTRIBUTING.md, CLAUDE.md, setup.sh, and issue templates.
Audit Reports Generates FORK_REPORT.md and SANITIZATION_REPORT.md, which provide details on copied files and security findings.

Frequently asked questions

Yes, if you want the skill to automatically create the public repository using `gh repo create`. Otherwise, you can push manually after reviewing the staging area.
It automatically excludes .git, node_modules, and other dependency or artifact directories to copy only the relevant source code.
The pipeline stops and prompts you to fix the issues. It generates a SANITIZATION_REPORT.md file with a "FAIL" verdict and a list of findings so you can resolve them.
Yes. The wizard asks you which license to use (MIT, Apache-2.0, etc.) when you start the pipeline and generates the corresponding LICENSE file.
Pipeline Open Source — Securely release private code with Claude AI

¿Prefieres escuchar el contenido? Genera la narración de audio con un clic.