open-source

Prepare a private repository for public release with Apache-2.0 licensing and secret removal.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/marcelocantos/skills --skill open-source
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-source
Source: https://github.com/marcelocantos/skills/tree/main/skills/open-source
Command: npx skills add https://github.com/marcelocantos/skills --skill open-source

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many private projects lack the necessary licensing, documentation, and clean history to be safely shared with the world, causing legal exposure and wasted effort when trying to open source them.

Core Features & Use Cases

  • Automated audit: Detects secrets, internal references, and license incompatibilities before publishing.
  • Fixes & documentation: Adds Apache‑2.0 LICENSE, updates .gitignore, inserts license headers, and generates comprehensive project documentation.
  • Seamless publishing: Creates the GitHub repository, pushes the cleaned code, and hands off to the release workflow for versioned binary distribution.

Quick Start

Run /open-source my-awesome-library to turn it into a public, release‑ready repository.

Frequently Asked Questions about open-source

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

FAQPage Schema
How do I prepare a private GitHub repository for public open-source release?

To prepare a private GitHub repository for public open-source release, you need to remove secrets, add licensing, and generate documentation. This skill automates that preparation by enforcing Apache‑2.0 licensing, updating .gitignore, and creating release artifacts alongside comprehensive docs.

What is the best way to audit code for secrets and internal references before publishing to GitHub?

The best way to audit code for secrets and internal references before publishing is to run an automated pre-publish check. This skill integrates an automated audit that detects secrets, internal references, and license incompatibilities to ensure safe public exposure.

Does open-sourcing a private repository retain the full commit history?

Yes, open-sourcing a private repository can retain the full commit history. This workflow preserves your entire commit history while applying Apache‑2.0 LICENSE files, inserting license headers, and cleaning the codebase for GitHub.

How do I add an Apache‑2.0 license and headers to an existing codebase?

To add an Apache‑2.0 license and headers to an existing codebase, you can automate the insertion during the open-sourcing workflow. This skill automatically adds the Apache‑2.0 LICENSE file, updates .gitignore, and inserts license headers across your project.

Can I create versioned release artifacts for macOS and Linux when open-sourcing a project?

Yes, you can create versioned release artifacts for macOS and Linux when open-sourcing a project. This skill hands off to a release workflow that generates and distributes versioned binary artifacts for both macOS and Linux platforms.