debug-build
Diagnose and fix build failures using structured error output.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Diagnose and fix build failures using structured error output.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Build, test, push, deploy, and verify with rollback through Git on failure.
Build and run AI apps and agents with Veryfront CLI
Development flywheel - autonomous cycle of run, observe, fix, verify. Use for continuous development with browser automation.
Build Veryfront apps. Use for real-time errors, route preview, HMR control, and scaffolding pages/APIs/components/AI tools.
Onboard to veryfront-code architecture, testing, conventions, and PR process.
Diagnose runtime errors by connecting to dev server via MCP.
| name | debug-build |
| description | Diagnose and fix build failures using structured error output. |
| metadata | {"version":"1.0.0"} |
Diagnose and fix build failures using structured error output.
Reproduce the failure
veryfront build --json
Capture the error envelope.
Get error context (via MCP)
Use vf_get_errors to get all current errors.
Use vf_get_debug_context for additional context.
Analyze errors Common build error patterns:
deno check outputdeno.json and veryfront.jsonFix and verify Apply the fix, then rebuild:
veryfront build --json
Run health check
veryfront doctor --json
deno.json imports map, verify file existsdeno check src/index.ts for detailed diagnosticsdeno.json from a fresh veryfront init