deploy
Enforces local testing before any deployment. MUST be used before running vercel, git push, or any deployment command. Prevents deploying untested code.
来源信息
- 仓库
- ChakshuGautam/games
- 最近来源活动
- 2026年1月4日 17:23
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 0
- 分支
- 1
安装方式
默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。
检查来源文件
决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- deploy
- description
- Enforces local testing before any deployment. MUST be used before running vercel, git push, or any deployment command. Prevents deploying untested code.
# Deploy Skill
**NEVER deploy without completing ALL steps below.**
## Required Workflow
Before ANY deployment (vercel, git push to main, etc.):
### 1. Build Locally
```bash
pnpm build
```
- Must complete with zero errors
- Check output for warnings
### 2. Start Local Dev Server
```bash
pnpm dev
```
- Server must start successfully
### 3. Test in Browser
- Open the local URL in Chrome DevTools MCP
- Test ALL changed functionality manually:
- Click buttons, verify they work
- Test keyboard input if applicable
- Submit forms, verify responses
- Check for console errors
### 4. Verify Tests Pass (if tests exist)
```bash
pnpm test
```
### 5. Only Then Deploy
After ALL above steps pass:
```bash
vercel --prod
```
## Rules
1. **NO SHORTCUTS** - Every step must be completed
2. **NO ASSUMPTIONS** - "It worked before" is not verification
3. **TEST AFTER CHANGES** - Any code change requires re-testing
4. **LOCAL FIRST** - Never deploy to see if something works
## Common Mistakes to Avoid
- Deploying immediately after build without browser testing
- Assuming dependency changes don't break anything
- Skipping keyboard/interaction testing
- Deploying to "check if it works on Vercel"
## When User Says "Deploy"
1. Ask: "Have you verified locally? Let me run through the checklist."
2. Run build
3. Start dev server
4. Test in browser via Chrome DevTools MCP
5. Only after confirming everything works, deploy
在 GitHub 查看