windsurf-reliability-patterns

# Windsurf Reliability Patterns ## Overview Reliability patterns for safe Cascade usage: Git checkpointing, incremental task scoping, validation gates, and rollback strategies. Cascade's multi-file editing is powerful but requires discipline to avoid breaking your codebase. ## Prerequisites - Windsurf with Cascade enabled - Git repository initialized - Test suite available - Understanding of Cascade Write mode ## Instructions ### Step 1: Always Commit Before Cascade The most important reliability pattern: create a clean Git checkpoint before every Cascade session. ```bash # Before starting a Cascade task git add -A && git commit -m "checkpoint: before cascade session" # After Cascade completes: git diff # Review all changes npm test && npm run typecheck # Validate # If good: git add -A && git commit -m "[cascade] add notification service" # If bad: git checkout -- . # Revert everything # Or selectively: git checkout -- src/problem-file.ts # Revert one file ``` ### Step 2: Use Feature Branches for Cascade Work ```bash # Create dedicated branch for each Cascade task git checkout -b cascade/add-notification-service # Do Cascade work on this branch # ... # If results are good: git checkout main && git merge cascade/add-notification-service # If results are bad: git checkout main && git branch -D cascade/add-notification-service # Clean slate, main branch untouched ``` ### Step 3: Sco...