windsurf-deploy-integration
Deploy Windsurf integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying Windsurf-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy windsurf", "windsurf Vercel", "windsurf production deploy", "windsurf Cloud Run", "windsurf Fly.io".
- License 许可
- MIT
- 最近更新
- 2026-03-20
- Stars
- ★ 4
- Forks
- 0
01 前言 Front Matter
- name
- windsurf-deploy-integration
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- version
- 1.0.0
- description
- Deploy Windsurf integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying Windsurf-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy windsurf", "windsurf Vercel", "windsurf production deploy", "windsurf Cloud Run", "windsurf Fly.io".
- allowed-tools
- Read, Write, Edit, Bash(vercel:*), Bash(fly:*), Bash(gcloud:*)
- compatible-with
- claude-code, codex, openclaw
03 SKILL.md 正文
Windsurf Deploy Integration
Overview
Deploy Windsurf extensions and configurations to teams. Windsurf, as a VS Code-based IDE, uses the standard extension deployment model.
Prerequisites
- Node.js and npm installed
vsceCLI for extension packaging (npm install -g @vscode/vsce)- Windsurf extension project with
package.json - Marketplace publisher account (for public distribution)
Instructions
Step 1: Package Extension
set -euo pipefail
# Install vsce
npm install -g @vscode/vsce
# Package extension as .vsix
cd my-windsurf-extension
vsce package
# Output: my-extension-1.0.0.vsix
Step 2: Extension package.json
{
"name": "my-windsurf-extension",
"displayName": "My Windsurf Extension",
"version": "1.0.0",
"engines": {
"vscode": "^1.85.0"
},
"activationEvents": ["onStartupFinished"],
"main": "./dist/extension.js",
"contributes": {
"commands": [{
"command": "myext.activate",
"title": "Activate My Extension"
}],
"configuration": {
"title": "My Extension",
"properties": {
"myext.apiKey": {
"type": "string",
"description": "API key for backend service"
}
}
}
},
"scripts": {
"build": "tsc -p ./",
"package": "vsce package",
"publish": "vsce publish"
}
}
Step 3: Distribute to Team
# Install .vsix manually in Windsurf
# Extensions sidebar > "..." menu > "Install from VSIX..."
# Or via command line
code --install-extension my-extension-1.0.0.vsix
Step 4: Shared Team Settings
// .vscode/settings.json (commit to repo)
{
"myext.apiKey": "",
"editor.formatOnSave": true,
"windsurf.cascade.enabled": true
}
// .vscode/extensions.json (recommended extensions)
{
"recommendations": [
"publisher.my-windsurf-extension",
"dbaeumer.vscode-eslint",
"esbenp.prettier-vscode"
]
}
Step 5: CI/CD for Extension
# .github/workflows/publish.yml
name: Publish Extension
on:
push:
tags: ["v*"]
jobs:
publish:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
- run: npm ci && npm run build
- run: npx vsce package
- run: npx vsce publish
env:
VSCE_PAT: ${{ secrets.VSCE_PAT }}
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Package fails | Missing files | Check files field in package.json |
| Extension not loading | Wrong engine version | Match engines.vscode to Windsurf version |
| Settings not applied | Wrong scope | Use workspace vs user settings appropriately |
| Publish rejected | Invalid publisher | Create publisher at marketplace.visualstudio.com |
Examples
Quick Package and Install
set -euo pipefail
npm run build && vsce package && code --install-extension *.vsix
Resources
Next Steps
For multi-environment setup, see windsurf-multi-env-setup.
Output
- Configuration files or code changes applied to the project
- Validation report confirming correct implementation
- Summary of changes made and their rationale
04 同仓库更多 Skills
azure-apim-architecture
Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.
apiops-deployment
Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep/Terraform), CI/CD pipelines (GitHub Actions/Azure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.
apim-policy-authoring
Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request/response processing logic.
api-security-review
Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.
jira-cli
Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.
calculator
Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.