From cc-rpi -- RPI Methodology
Promotes disciplined CI workflow: push accountability, background CI monitoring, sequential verification, pre-commit checks, and config change blast radius testing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cc-rpi:ci-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use the branch that is currently under CI verification. In a
Use the branch that is currently under CI verification. In a
develop/main topology this is often develop. In a main-only repo
it is usually the temporary branch or PR branch being validated before
merge.
Wrong -- push and move on:
git push origin <branch-under-test>
# Start next task immediately, never check CI
Right -- spawn background agent to monitor CI:
git push origin <branch-under-test>
# Background agent:
gh run list --branch <branch-under-test> --limit 1
# If CI fails: investigate with gh run view <id> --log-failed
# Fix and re-push. The push isn't done until CI is green.
Wrong -- run typecheck, lint, test as parallel tool calls:
# Parallel call 1: pnpm run typecheck
# Parallel call 2: pnpm run lint
# Parallel call 3: pnpm run test
# If one fails, all parallel calls are killed (Error #1)
Right -- chain sequentially with semicolons:
pnpm run typecheck 2>&1; pnpm run lint 2>&1; pnpm run test 2>&1
Wrong -- commit first, discover failures from pre-commit hook:
git commit -m "feat: add feature"
# Pre-commit hook fails: lint errors, type errors
Right -- run checks before committing:
pnpm run typecheck 2>&1; pnpm run lint 2>&1
git add <files> && git commit -m "feat: add feature"
Wrong -- change tsconfig and continue coding:
# Edit tsconfig.json
# Continue implementing next feature
# Discover 200 type errors at commit time
Right -- run full test suite immediately after config changes:
# Edit tsconfig.json
pnpm run typecheck 2>&1; pnpm run lint 2>&1; pnpm run test 2>&1
# Fix any breakage before proceeding
npx claudepluginhub juan294/cc-rpi --plugin cc-rpiCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.