safe-public-release
适用于开源或导出前的敏感数据检测与合规流程化
会访问/修改仓库文件并可能读取私有凭证，需谨慎授权
把私有产物清理脱敏后安全发布为公开包/仓库
把私有代码、agent skill、prompts、数据集或其他产物清理脱敏后安全发布到公开包或仓库。包含来源清单、许可证与安全/隐私审查、显式允许项、干净的打包与审批演练，以及发布后新仓库的验证步骤，目的是防止泄露密钥、个人数据或不可再分发的第三方内容。适合要把内部项目 open-source 或对外共享时使用。
▸ 展开 SKILL.md 英文原文
Use when publishing, open-sourcing, exporting, sanitizing, or moving code, agent skills, prompts, templates, fixtures, datasets, workshop assets, or other artifacts from a private repository, vendor/runtime environment, or mixed working directory into a public repository or registry. Builds a provenance inventory, license/security review, explicit allowlist, clean staging package, approval dry run, and fresh public clone/install smoke. Triggers on "open source this", "publish these skills", "make this repo public", "export and sanitize", "подготовь публичный релиз", "выложи скиллы", "опенсорсни", "санитизируй и опубликуй". NOT for ordinary upstream bugfix PRs, vulnerability disclosure, or creating a corp-* department.
帮我安装这个 skill：https://raw.githubusercontent.com/serejaris/personal-corp-skills/main/skills/safe-public-release/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/serejaris/personal-corp-skills/main/skills/safe-public-release/SKILL.md"# Safe Public Release Turn a private, vendor-provided, runtime-generated, or mixed artifact into a public package without leaking secrets, private state, or material that cannot be redistributed. One pipeline: `intent → owner issue tree → inventory → provenance → license → security/privacy → allowlist → clean package → approval → publish → fresh public verification → maintenance` The skill is **allowlist-first**. Never copy a whole runtime/private directory and hope denylist cleanup finds everything. ## Hard safety boundary Publishing is an outward mutation. Before creating a public repository, changing visibility, pushing a release, or publishing to a registry: 1. complete the invent