oss-launchlisted

# oss-launch Turn a repo into a credible open-source project: scan what exists, fill the gaps with adapted (not boilerplate) files, then optionally launch it. `templates/` holds the payload this skill writes into a USER's repo. The root files (README, LICENSE, etc.) describe oss-launch itself. Never confuse the two. ## Run (when invoked) Work top to bottom. Do not dump all files blindly; scan first, then fill only real gaps. **0. Scan the repo** (details: `references/scan.md`) - Stack: `package.json` / `pyproject.toml` / `Cargo.toml` / `go.mod` / `composer.json` / `*.csproj` -> language, package manager, test/build/lint commands. - Existing OSS files present vs missing: README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, CHANGELOG, `.gitignore`, `.github/` templates, CI workflows. - Git: `git remote -v` -> `{{OWNER}}/{{REPO}}` + default branch. `gh repo view` -> public? - Declared license (`package.json` "license" field / existing `LICENSE`). - Demo asset present? (screenshot / gif in README or `docs/`). - **Secret + brand-leak scan** (do this every time, even private->public): `.env`, API keys, tokens, hardcoded absolute/personal paths, internal-only references. If anything leaks, STOP and surface it before generating or publishing anything. **1. Report** the findings and a gap table. Run the audit for the checklist: ```bash bash scripts/audit.sh . ``` **2. Ask only what cannot be inferred** (batch into one question round): license (if undeclared), autho