opensource-pipeline

Fork a private codebase, strip secrets, and generate open-source release artifacts.

Updated Sep 13, 2025

Search Tags:#github #opensource #security hardening #secrets scanning #release packaging #repo sanitization

Ready to run

npx skills add https://github.com/llmh333/employee_management_spring --skill opensource-pipeline-llmh333

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents accidental leaks of secrets or sensitive data when turning a private project into a safe public open-source release.

Core Features & Use Cases

Fork & Secret Stripping: Creates a staging fork that removes credentials and cleans internal references.
Sanitization Gate: Runs comprehensive scans (secrets, PII, dangerous files, config completeness, and git history audit) and produces a pass/fail report.
Release Packaging: Generates standardized public-ready docs and artifacts (GEMINI.md, setup.sh, README, LICENSE, contributing guidance, and issue templates).

Quick Start

Tell the AI to prepare your project for release by running: /opensource fork PROJECT.

Frequently Asked Questions about opensource-pipeline

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

FAQPage Schema

How do I sanitize a private GitHub repository before making it public?▼

To sanitize a private GitHub repository before making it public, you can fork the repo, strip secrets, audit git history, and generate a pass/fail staging report before packaging release artifacts.

What is the best way to strip secrets and credentials from git history for open source release?▼

Stripping secrets and credentials from git history involves running a sanitizer pipeline that scans for secrets, PII, and dangerous files, producing a gated pass/fail report before generating public release artifacts.

How do I package a private codebase into open-source release artifacts?▼

Packaging a private codebase into open-source release artifacts involves generating standardized public-ready docs and files, including GEMINI.md, setup.sh, README, LICENSE, and contribution materials, after passing sanitization checks.

Does the repo sanitization process check for PII and dangerous files?▼

Yes, the repo sanitization process checks for PII and dangerous files by running a comprehensive sanitization gate that audits secrets, PII, config completeness, and git history before allowing release packaging.

Can I generate contribution guidelines and issue templates when open sourcing a private project?▼

Yes, you can generate contribution guidelines and issue templates when open sourcing a private project as part of the release packaging stage, which also produces README, LICENSE, and setup.sh artifacts.

What happens if the sanitizer fails during the open source packaging pipeline?▼

If the sanitizer fails during the open source packaging pipeline, the process halts the release packaging stage, preventing the generation of public-ready artifacts until the secrets, PII, or dangerous files are resolved.