From cc-rpi -- RPI Methodology
Provides rules for safe production deployments including rollback-first recovery, dependency batching, CI cost awareness, and framework upgrade verification.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cc-rpi:deployment-safetyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Wrong -- merge Dependabot PR thinking it's cleanup:
Wrong -- merge Dependabot PR thinking it's cleanup:
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:
# 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
Wrong -- merge N PRs one-by-one (O(n^2) rebase cascade):
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:
# 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
Wrong -- push partial work to see if CI passes:
git push # 9 workflows triggered, guess and check
Right -- test locally, push once:
pnpm run typecheck 2>&1; pnpm run lint 2>&1; pnpm run test 2>&1
git push # confident it works
Wrong -- merge after CI passes (CI != production):
gh pr merge 99 --squash # CI green, serverless runtime crashes
Right -- verify on preview deployment first:
# Push to non-main branch -> preview URL
# Verify: site loads, API routes respond, health checks pass
# Only then merge to main
Wrong -- deploy fixes to prod while investigating:
vercel deploy --prod # fails, deploy again, fails again
Right -- roll back first, investigate second:
vercel rollback # Step 1: restore service immediately
# Step 2: investigate on non-production (logs, preview URL)
# Step 3: fix on the integration path, verify on preview,
# then merge to the production branch
Before any CI run, deployment, or API call:
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.
Creates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.
npx claudepluginhub juan294/cc-rpi --plugin cc-rpi