debug-runtime

Connect to a local dev server via MCP to diagnose runtime errors.

9|1|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/veryfront/veryfront-code --skill debug-runtime
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-runtime
Source: https://github.com/veryfront/veryfront-code/tree/main/cli/mcp/skills/debug-runtime
Command: npx skills add https://github.com/veryfront/veryfront-code --skill debug-runtime

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps diagnose runtime errors by providing a direct connection to the dev server, allowing for efficient troubleshooting and issue resolution.

Core Features & Use Cases

  • Runtime Error Diagnostics: Connects to the dev server to diagnose and fix runtime errors.
  • Dev Server Connection: Connects to the dev server via MCP to access error logs and debug context.
  • Use Case: When encountering a runtime error in a development environment, this Skill can be used to quickly identify the issue and apply fixes.

Quick Start

Use the debug-runtime skill to get a debug context for the current runtime errors.

Frequently Asked Questions about debug-runtime

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose runtime errors from my dev server?

To debug runtime errors, connect directly to your local development server via MCP to retrieve error logs, stack traces, and request context for efficient troubleshooting.

What do I need to access error logs through an MCP interface?

You need a running local development server and access to the MCP interface to retrieve debug context and diagnose runtime errors effectively.

Can I use this to get stack traces for runtime errors in my development environment?

Yes, connecting to your dev server through MCP provides direct access to stack traces and request context to help you quickly identify and fix runtime errors.

What's the best way to troubleshoot local development server issues?

Troubleshooting local development server issues is best done by establishing a direct connection to retrieve error logs and debug context, allowing for quick issue identification and resolution.

Why does diagnosing runtime errors require a running dev server?

Diagnosing runtime errors requires a running dev server because the Skill establishes a direct connection to access live error logs, stack traces, and request context from your local environment.