tessl-fe/rapid-deploy
Use for deployments, shipping, releasing, pushing to production, hotfixes, rollbacks, and any task related to getting code live
94
97%
Does it follow best practices?
Impact
86%
1.32xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
93%
40%PR Readiness Report for Forge Dashboard
Pre-merge readiness checklist for a Vercel-deployed PR
npm run build step
100%
100%
Build failure blocks merge
62%
100%
Env vars in Vercel before merge
70%
100%
Vercel Production env vars
75%
100%
NEXT_PUBLIC keys mentioned
0%
100%
.env.example update required
100%
100%
Console.log check command
90%
100%
Preview URL verification
20%
100%
Preview test checklist items
50%
100%
Re-deploy preview after env fix
10%
100%
No extra general checks
10%
30%
100%
23%Build Failure Triage Guide
Vercel build failure triage guide
TypeScript fix instruction
100%
100%
Env var → Vercel settings fix
100%
100%
NEXT_PUBLIC_DATA_URL named
100%
100%
Module not found → npm install
0%
100%
package-lock.json commit
0%
100%
Case-sensitivity for ENOENT
100%
100%
Build logs location
100%
100%
Vercel dashboard path
100%
100%
Does NOT suggest --noEmit workaround
90%
100%
No unrelated troubleshooting
100%
100%
67%
2%Code Review: Flag Issues Blocking Merge
PR review flagging console logs and missing env vars
Console.log flagged in TSX
100%
100%
Console.error flagged
100%
100%
Console.log in settings.ts flagged
100%
100%
Console check command referenced
0%
0%
Missing .env.example update flagged
100%
100%
env.example must update in same PR
50%
30%
Vercel env var must be added
0%
33%
PR blocked conclusion
100%
100%
No false positives
0%
10%
Remediation steps included
100%
87%
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6