windsurf-prod-checklist
Perform a structured production readiness audit for Windsurf team or enterprise rollouts.
Install
mkdir -p .claude/skills/windsurf-prod-checklist && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4229" && unzip -o skill.zip -d .claude/skills/windsurf-prod-checklist && rm skill.zipInstalls to .claude/skills/windsurf-prod-checklist
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Execute Windsurf production readiness checklist for team and enterpriseKey capabilities
- →Configure `.windsurfrules` and `.codeiumignore` per repository
- →Enforce security settings like SSO/SAML and zero-data-retention
- →Establish AI usage policies and commit conventions
- →Set up developer machines with Windsurf and recommended extensions
- →Monitor adoption, quality, and efficiency metrics from the Admin Dashboard
- →Execute rollback procedures by disabling Cascade
How it works
This skill guides through a checklist for Windsurf production rollout, covering configuration, security, team onboarding, and monitoring. It provides scripts and instructions for each phase.
Inputs & outputs
When to use windsurf-prod-checklist
- →Audit repository workspace settings
- →Verify enterprise SSO and security configuration
- →Configure environment-specific ignore files
- →Ensure AI usage policies are documented and enforced
About this skill
Windsurf Production Checklist
Overview
Complete checklist for rolling out Windsurf to production teams. Covers workspace configuration, security hardening, team onboarding, and monitoring.
Prerequisites
- Windsurf plan selected (Pro, Teams, or Enterprise)
- Admin access to Windsurf dashboard
- Git repositories identified for rollout
- Team agreement on AI usage policy
Instructions
Phase 1: Pre-Deployment Configuration
Workspace Config (per repository):
-
.windsurfrulescreated with project stack, patterns, and constraints -
.codeiumignoreexcludes secrets, build artifacts, and large binaries -
.windsurf/rules/contains glob-triggered rules for file-type-specific patterns - Workspace settings committed to
.windsurf/settings.json
Security:
- Telemetry configured per company policy
-
.codeiumignorecovers all secret file patterns - Autocomplete disabled for secret-containing file types (.env, .key)
- Enterprise: SSO/SAML configured and enforced
- Enterprise: zero-data-retention verified with Codeium
Team Policy:
- AI usage policy document created and shared
- Commit convention for AI-generated code established (e.g.,
[cascade]prefix) - Code review requirements for AI-generated changes defined
- Competing AI extensions disabled (Copilot, TabNine)
Phase 2: Team Onboarding
Per-Developer Setup:
#!/bin/bash
# scripts/setup-windsurf.sh — run on each developer machine
echo "Setting up Windsurf for this project..."
# Verify Windsurf is installed
windsurf --version || { echo "Install Windsurf first: https://windsurf.com/download"; exit 1; }
# Verify config files exist
[ -f .windsurfrules ] || echo "WARNING: .windsurfrules missing"
[ -f .codeiumignore ] || echo "WARNING: .codeiumignore missing"
# Install recommended extensions
windsurf --install-extension esbenp.prettier-vscode
windsurf --install-extension dbaeumer.vscode-eslint
# Disable conflicting extensions
windsurf --disable-extension github.copilot 2>/dev/null || true
echo "Setup complete. Open project folder (not monorepo root) for best AI context."
Training Checklist:
- Demo: Supercomplete (Tab) vs Cascade (Cmd+L) vs Command (Cmd+I)
- Demo: Write mode vs Chat mode
- Demo: @ mentions for file context
- Demo: Turbo mode with allow/deny lists
- Demo: Previews for UI development
- Demo: Git checkpoint before Cascade workflow
- Share:
.windsurfrulesexplained - Share: Credit system and model selection
Phase 3: Monitoring and Optimization
Admin Dashboard Monitoring:
# Metrics to track weekly (Admin Dashboard > Analytics)
metrics:
adoption:
- active_users_vs_total_seats # target: >80%
- daily_active_users # trend: increasing
quality:
- completion_acceptance_rate # target: >25%
- cascade_success_rate # target: >70%
efficiency:
- credits_consumed_per_user # watch for outliers
- tasks_completed_per_day # proxy for productivity
Quarterly Review:
- Audit seat utilization -- downgrade inactive seats
- Review
.windsurfrules-- update with new patterns - Check for new Windsurf features in changelog
- Survey team satisfaction and pain points
- Analyze credit usage patterns
Phase 4: Rollback Procedure
If Windsurf causes issues:
1. Disable Cascade for team: Admin Dashboard > Features > Cascade > Off
2. Developers can still use Supercomplete (non-agentic)
3. Switch to manual coding while investigating
4. Review recent Cascade-generated commits for issues
5. File support ticket with debug bundle (see windsurf-debug-bundle)
Error Handling
| Issue | Severity | Mitigation |
|---|---|---|
| Cascade generates broken code | Medium | Enforce tests-pass-before-merge policy |
| AI exposes secrets in suggestions | High | Audit .codeiumignore, rotate exposed secrets |
| Team not adopting | Low | Training session, share productivity data |
| Credits exhausted mid-sprint | Medium | Monitor usage, buy additional credits proactively |
Examples
Recommended Extension Set
// .vscode/extensions.json (also works in Windsurf)
{
"recommendations": [
"esbenp.prettier-vscode",
"dbaeumer.vscode-eslint",
"biomejs.biome"
],
"unwantedRecommendations": [
"github.copilot",
"tabnine.tabnine-vscode"
]
}
Quick Compliance Check
set -euo pipefail
echo "Config: $([ -f .windsurfrules ] && echo 'OK' || echo 'MISSING')"
echo "Ignore: $([ -f .codeiumignore ] && echo 'OK' || echo 'MISSING')"
echo "Rules: $([ -d .windsurf/rules ] && echo 'OK' || echo 'MISSING')"
Resources
Next Steps
For version upgrades, see windsurf-upgrade-migration.
When not to use it
- →When Windsurf causes issues that require switching to manual coding
Prerequisites
Limitations
- →Cascade generating broken code requires enforcing a tests-pass-before-merge policy
- →AI exposing secrets in suggestions requires auditing `.codeiumignore` and rotating exposed secrets
- →Credits exhaustion mid-sprint requires monitoring usage and proactive credit purchase
How it compares
This skill provides a structured checklist and automated scripts for Windsurf production deployment, ensuring adherence to best practices, unlike ad-hoc deployments that may miss critical configuration or security steps.
Compared to similar skills
windsurf-prod-checklist side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| windsurf-prod-checklist (this skill) | 1 | 27d | Review | Intermediate |
| django-verification | 5 | 4mo | Review | Intermediate |
| coderabbit-deploy-integration | 1 | 27d | Review | Intermediate |
| push | 0 | 3mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
django-verification
affaan-m
Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.
coderabbit-deploy-integration
jeremylongshore
Deploy CodeRabbit integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying CodeRabbit-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy coderabbit", "coderabbit Vercel", "coderabbit production deploy", "coderabbit Cloud Run", "coderabbit Fly.io".
push
robinbeier
Push the current issue branch, create or update the GitHub pull request, link
hotfix
akiojin
Execute the hotfix workflow when the user asks `hotfix` or `/hotfix`: create a hotfix branch from main, guide fix+checks, open PR to main, and confirm patch release.
pr
meshtastic
Push the current branch and open a draft PR for Meshtastic-Android the repo way — baseline verified first, body drafted per .github/copilot-pull-request-instructions.md (WHY-first, categorized changes), screenshots embedded via commit-pinned raw URLs. Use whenever work is ready to go up as a PR.
risk-review
LynxPardelle
Repo-local findings-first review workflow for Zoolanding Lambda diffs, deploy candidates, and contract changes. Use when reviewing for bugs, regressions, rollout risk, weak validation, or missing tests.