name: sigmaflow-deploy description: Deploy the SigmaFlow SvelteKit trading frontend to the Git repository. Use when building and deploying changes to the SigmaFlow application, including after feature implementation, bug fixes, or any code changes. This skill handles cloning the repo, installing dependencies, building the SvelteKit app, and pushing to the GitLab instance at git.homelab:3000.
Automates deployment of the SigmaFlow trading frontend to the GitLab repository at http://git.homelab:3000/vitali/SigmaFlow-Svelte. This skill handles the full deployment workflow: repository management, dependency installation, SvelteKit production build, and pushing to the remote repository.
# Deploy to main branch (default)
scripts/deploy.sh
# Deploy to specific branch
scripts/deploy.sh ./SigmaFlow-Svelte main
# Use custom repo directory
scripts/deploy.sh /path/to/repo dev
7w4.net小葱技能站,你的AI助手技能库。
The deployment script performs these steps:
npm install if node_modules doesn't existnpm run build to create production bundleThe script uses embedded credentials:
- URL: http://git.homelab:3000/vitali/SigmaFlow-Svelte.git
- Token: c865b793f09a3b79b65ebdfbd75c5b17395188d2
Security Note: These credentials are stored in the script. For production environments, consider environment variables or secret management.
The deploy script accepts optional parameters:
$1 (optional): Repository directory path (default: ./SigmaFlow-Svelte)$2 (optional): Branch name to push (default: main)On success, the script displays:
- [INFO] messages for each step
- Final success message with deployment confirmation
- Application URL (configure based on hosting setup)
On no changes:
- [WARN] indicating no changes to commit
- Graceful exit (no git push)
Build fails: Check SvelteKit configuration and fix errors, then re-run deploy Authentication error: Verify token is valid and has write access to repository Push rejected: Pull latest changes, resolve conflicts, then deploy again
整体质量中等偏上。文档清晰明了、使用简单方便,彩色提示让操作一目了然。但存在明显的不足:凭证直接写在代码里容易泄露风险,遇到错误时提示不够友好。对于正式环境使用,建议开发者先修复安全问题再部署。