1---2name: ship-package3description: Use before local release or handoff to prepare reproducible Docker/release/GitHub packages with secret checks, rollback notes, and verification evidence.4---56# Ship Package7## Claude Code Adaptation89- This copy is prepared for Claude Code personal or project skills.10- Resolve bundled files relative to ${CLAUDE_SKILL_DIR} when Claude Code exposes it; otherwise use the local skill directory.11- Map old agent/tool wording to the closest Claude Code capability by intent.1213## Workflow141. Read product spec, release notes, Docker files, README, `.env.example`, and verification output.152. Run release checks: secret scan, required docs, build/test hints, launch scripts, rollback notes.163. Write `release_check_report.md` and report final delivery paths.174. Package only source, docs, scripts, and safe sample data.185. Exclude `.env`, tokens, sessions, account files, raw company data, caches, and generated secrets.1920## Hard rules21- Never ship `.env`, API keys, Weixin tokens, cookies, sessions, or company raw data.22- Do not claim a package is runnable without a fresh verification command.23- Release notes must include exact paths, commands, and known gaps.24- Prefer reproducible scripts over manual Finder-only operations.
WyattJY