domains / families / security / open-sourcing

open-sourcing

separate

This skill should be used when the user asks to "open source this project", "prepare this repository for public release", "make this repo public", "check open-source readiness", "choose a license for this project", or "set up release automation" ahead of a public launch. Provides a release-readiness workflow covering secrets hygiene, licensing, documentation, CI, and language-specific packaging.

When to use

• Making a private repository public
• Auditing an existing public repository for release quality ("make it
• Choosing a license for a project
• Setting up packaging, versioning, or release automation ahead of a public

When not to use

• Routine development on an already-released project (no release event)
• Auditing third-party code for vulnerabilities (use a security-review skill)
• Publishing a package from a repository that will stay private — only the

Skill page

Source