Open-sourcing guides an agent through preparing a repository for public release so that an outsider can build, use and contribute to it, and nothing sensitive ships with it. The steps run in a fixed order, starting with a secrets audit because its outcome decides whether the repository can be published or must be recreated.
It then covers documentation, license selection, tests and CI hardening, repository settings, release tagging and per-language packaging. A Trail of Bits profile is loaded automatically when the repository belongs to that organization.
What You Get
- A secrets audit step that tells you when a fresh repository is the safer route than rewriting history
- A printed readiness checklist covering README, LICENSE, CONTRIBUTING, SECURITY policy, CI, tests and semver tags
- License guidance with SPDX metadata rules and a consistency check between LICENSE, package metadata and README
- Per-language reference notes for Python, C/C++, Rust, Go, JavaScript and Ruby
- A final review from an outsider’s point of view: clean clone, build from the README, re-run the checklist
Common Use Cases
- Making a private repository public
- Auditing an existing public repository for release quality
- Choosing a license for a new project
- Setting up CI-driven releases and trusted publishing before a launch
What Makes It Unique
The skill puts the secrets audit before everything else and lists the excuses to reject, such as a revoked key or a history rewrite. It treats the readiness checklist as discussion prompts for the maintainer, and it tells the agent to keep working formatters and linters in place. An organization overlay for license policy and publishing accounts is applied when detected.
Under The Hood
The agent reads SKILL.md and loads reference files for licensing, the organization profile and the detected language only when needed. It runs two bundled shell scripts. One inspects git remotes and recent committer emails to pick a profile. The other checks for common files and lists tracked files that often hold secrets. It also suggests running secret scanners, a workflow audit tool and a workflow linter on the repository, and it may edit repository files such as LICENSE, README, SECURITY.md and workflow files. No network calls are made by the bundled scripts.