github-safe-publisherlisted

# GitHub Safe Publisher ## Overview Use this skill to turn private project material into public-safe GitHub artifacts such as case studies, skill releases, README updates, demo notes, and example prompts. The skill produces a safety verdict and concrete next steps; it must not auto-commit, auto-push, publish, upload, send, or share anything without explicit human review. ## Workflow 1. Identify the intended public artifact: skill, case study, README section, demo screenshot note, example prompt, template, or changelog. 2. Read `references/public-safety-boundaries.md` before deciding what can be reused, generalized, or removed. 3. Work from a copy or rewritten summary, not the private original. Prefer a sanitized draft folder before touching a public repo. 4. Remove or replace sensitive details: credentials, account data, client material, raw prompts, logs, databases, exports, local paths, private source, and screenshots with private UI. 5. Run the scanner on the proposed public folder: ```bash python scripts/scan_public_safety.py path/to/public-candidate ``` 6. Read `references/release-workflow.md` before staging changes. 7. Require manual review of `git status --short`, the unstaged diff, and the staged diff before any commit or push. ## Verdicts Return one of these verdicts in every review: - `BLOCK`: Real secrets, credentials, raw private data, client-identifying material, local machine paths, databases, exports, logs, or unintended source files are present. - `RE