Opensource Release

What This Skill Does

The Opensource Release skill by jini92 is a specialized utility designed to assist developers in transitioning private repositories into secure, public open-source projects. It acts as an automated audit and sanitization assistant, ensuring that sensitive environment variables, hardcoded local file paths, and personal system artifacts are scrubbed from the codebase and git history before the repository is made visible to the public. By orchestrating a multi-step checklist that includes deep file scanning, documentation audit, and git history pruning, the skill helps prevent the accidental leaking of credentials or personally identifiable information (PII).

Installation

To integrate this skill into your environment, run the following command in your OpenClaw terminal: clawhub install openclaw/skills/skills/jini92/opensource-release Once installed, the agent will have the permissions necessary to scan your workspace, execute git commands, and utilize the GitHub CLI to update repository visibility settings.

Use Cases

This skill is ideal for:

1. Individual developers moving projects from local development to public GitHub repositories.
2. Teams performing security audits on legacy codebases before open-sourcing them to ensure no API keys are hardcoded.
3. Open-source maintainers who need a systematic way to clean git history that contains accidentally committed configuration files or cache artifacts.
4. Developers who want to ensure that documentation files do not reveal their local file structure or username architecture.

Example Prompts

1. "OpenClaw, I want to release my current project to GitHub. Can you run the full open source sanitization workflow to make sure I'm not exposing any secrets?"
2. "I need to make this repo public. Please scan my code for absolute paths and hardcoded API keys first."
3. "Sanitize this repository for a public release. Clean the history of all cache files and then push a fresh main branch to origin."

Tips & Limitations

• Always perform a manual final check of your .env or configuration files, even after the scan, as some secrets might be obfuscated.
• Choosing the correct history strategy is crucial: use 'clean push' if you are okay with resetting the commit history, or use professional tools like BFG Repo Cleaner if you must retain specific commit history while scrubbing only sensitive data.
• Ensure you have the GitHub CLI (gh) authenticated locally, as the final visibility change step requires active authorization tokens for the repo owner.