opensource-pipeline

Name: opensource-pipeline
Availability: InStock
Author: cescrafli

Automates fork, sanitize, package pipeline for private-to-public GitHub releases.

Updated Mar 26, 2026

Search Tags:#automation #security #sanitization #packaging #governance #open-source #fork

Ready to run

npx skills add https://github.com/cescrafli/compyrasion --skill opensource-pipeline-cescrafli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: opensource-pipeline
Source: https://github.com/cescrafli/compyrasion/tree/main/skills/opensource-pipeline
Command: npx skills add https://github.com/cescrafli/compyrasion --skill opensource-pipeline-cescrafli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open-source pipelines enable safely releasing private projects to the public by removing secrets, validating code, and packaging artifacts in a repeatable process.

Core Features & Use Cases

Fork the repository while stripping secrets and sensitive references.
Sanitize the fork to detect secrets, PII, and internal references, with a clear remediation report.
Package the sanitized code into a ready-to-publish set (CLAUDE.md, setup.sh, README, LICENSE, etc.) and stage it for GitHub publication.
Use cases: teams preparing private projects for open source, security-conscious organizations releasing internal tools, or individuals wanting a compliant public release.

Quick Start

Run the open-source pipeline on your local project to stage a public-ready release.

Frequently Asked Questions about opensource-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I safely open-source a private repository without exposing secrets?▼

Safely open-source a private repository by using an automated 3-stage pipeline that forks the codebase, sanitizes it to strip secrets and internal references, and packages it with the necessary public release files.

What is the best way to sanitize code for public release?▼

The best way to sanitize code for public release is through an automated pipeline stage that detects secrets, PII, and internal references, generating a clear SANITIZATION_REPORT.md to guide remediation before packaging.

How do I prepare a private codebase for GitHub publication?▼

Prepare a private codebase for GitHub publication by running a packaging stage that generates required artifacts like CLAUDE.md, setup.sh, README, and LICENSE, staging the output for compliant public release.

Can I automate the process of forking and cleaning internal tools for public use?▼

Yes, you can automate the process of forking and cleaning internal tools via a configurable pipeline that forks the repository, strips sensitive references, and packages the sanitized code for public release.

What files are needed to publish an open-source project from a private codebase?▼

Publishing an open-source project requires packaging artifacts like CLAUDE.md, setup.sh, README, and LICENSE, which the pipeline generates automatically alongside status checks and staging reports.

Does the open-source pipeline provide reports on what secrets or references were removed?▼

Yes, the open-source pipeline generates a SANITIZATION_REPORT.md detailing detected secrets, PII, and internal references, alongside a FORK_REPORT.md to provide clear visibility into the remediation process.