Pr Ship

What to check before installing or running this skill: - Review scripts/test-update-pipeline.sh line-by-line. It contains hardcoded paths (/home/dev/.openclaw/skills/pr-ship, $HOME/.openclaw/cron/jobs.json) and will read local cron config and git metadata — ensure those checks are acceptable for your environment. - The SKILL.md and playbook assume many command-line tools (git, grep, sed, node, jq, python3, pnpm, clawhub). The skill does not declare these; make sure your environment provides them and consider running in a sandbox or a dedicated dev container. - The skill's update flow (clawhub update, cron-driven CURRENT-CONTEXT.md refresh) will perform network git operations (git fetch upstream). Confirm the remote origins are trustworthy and that no credentials will be accidentally exposed or used for unintended pushes. - If you plan to enable automated updates (cron/clawhub), run the update script manually first in a safe environment and verify it does not perform unexpected writes or network pushes (the test script explicitly warns cron should not run git push or clawhub publish automatically). - The skill is coherent with its stated purpose, but because it touches system files and assumes an update pipeline, treat it as potentially impactful: run reviews locally, verify remote provenance (the package.json points to a GitHub repo), and avoid enabling automatic cron updates until you confirm the workflow and remotes. If you want, I can extract the specific lines from the script that read host paths and network operations, or produce a short checklist of commands to run locally to validate behavior safely.