← ClaudeAtlas

deployment-safetylisted

Production deployment rules, rollback-first recovery, dependency batching, CI cost awareness, framework upgrade verification, fallback observability, and GitHub repo settings standardization.
juan294/cc-rpi · ★ 5 · AI & Automation · score 77
Install: claude install-skill juan294/cc-rpi
# Deployment Safety ## Merging to Main Wrong -- merge Dependabot PR thinking it's cleanup: ```bash gh pr merge 42 --merge # Dependabot targets main = production deploy ``` Right -- move the update onto the non-production integration path, close the PR, and release normally: ```bash # develop/main topology: git checkout develop && git cherry-pick <commit> gh pr close 42 # release via develop -> main # main-only topology: git checkout -b chore/dependency-updates main git cherry-pick <commit> gh pr close 42 # validate on branch/PR before merging back to main ``` ## Dependency Batching Wrong -- merge N PRs one-by-one (O(n^2) rebase cascade): ```bash gh pr merge 1 && gh pr merge 2 && gh pr merge 3 # 7 PRs x 9 workflows = ~189 wasted CI runs ``` Right -- batch into a single branch: ```bash # develop/main topology: git checkout -b chore/dependency-updates develop # main-only topology: git checkout -b chore/dependency-updates main # Apply all updates, run CI once, merge one PR ``` ## CI Cost Awareness Wrong -- push partial work to see if CI passes: ```bash git push # 9 workflows triggered, guess and check ``` Right -- justify the run before triggering it, then push once: ```text Before any CI run, deployment, or API call, ask: 1. Is this needed? (Can I achieve this locally?) 2. Is this justified? (Does this advance the task?) 3. Is this verifiable? (Will I know if it succeeded?) If any answer is "no" -- do not proceed. ``` ```bash pnpm run typecheck 2>&1; pnpm