Open Source Release

Convert a private repository to public open-source. Use when making a repo public, sanitizing personal info from code/docs/git history, or preparing a projec...

This skill is a focused checklist for making a repo public and cleaning history, but it includes destructive git commands. Before using: 1) Make a full mirror backup (git clone --mirror) or work on a copy; 2) Test history-rewriting commands on a clone and confirm tool availability (git, gh, BFG/git-filter-repo); 3) Check CI, package registries, webhooks, and external services for stored secrets or tokens (not just code files); 4) Coordinate with collaborators — force-pushes and branch deletions rewrite history and can disrupt others; 5) If you are on Linux/macOS, translate PowerShell examples or run them in a suitable environment. If you want, I can produce a non-destructive dry-run script and a checklist tailored to your repository (list remotes, create mirror, run safe scans) before you perform any irreversible actions.

Type: OpenClaw Skill Name: opensource-release Version: 1.1.0 The skill is designed to convert a private repository to public, including sanitizing git history and changing visibility. While the stated purpose is benign, the skill instructs the agent to execute high-impact commands such as `git push origin main --force` and `gh repo edit {owner}/{repo} --visibility public`. These commands, found in `SKILL.md`, carry significant risk of irreversible data loss or accidental public exposure of sensitive information if the sanitization steps are incomplete or the commands are misused. The prompt instructions themselves are not malicious, but the inherent risk of the actions makes the skill suspicious.