skills.rest
fusebase-dev
fusebase-devOFFICIAL
Explore all skills by this author →
GitHub

dev-debug-logs

Locate and interpret runtime logs for local FuseBase app debugging.

6|Updated May 29, 2026
Search Tags:#api troubleshooting#local development#backend logs#log debugging#fusebase#dev-debug-logs#frontend logs
One-click install
npx skills add https://github.com/fusebase-dev/fusebase-flow --skill dev-debug-logs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-debug-logs
Source: https://github.com/fusebase-dev/fusebase-flow/tree/main/.agents/skills/dev-debug-logs
Command: npx skills add https://github.com/fusebase-dev/fusebase-flow --skill dev-debug-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When running FuseBase apps locally with the fusebase dev start CLI, developers often waste time searching through scattered log outputs to find the root cause of frontend errors, backend failures, or broken API requests, with no clear guidance on which log file corresponds to which symptom.

Core Features & Use Cases

  • Symptom-based log routing: Clear rules for which log file to inspect for common issues like browser console errors, backend startup failures, proxied API problems, and frontend dev server build errors.
  • Cross-service log correlation: Guidance on linking browser errors to API request/response records and backend logs using shared request IDs to trace issues across the full stack.
  • Pre-built troubleshooting runbook: A step-by-step guide for resolving common CORS and PostgreSQL Gate flow failures without modifying app code first. Use case: For example, if a user sees a generic fetch error in the UI when testing a PostgreSQL-backed feature, this skill walks them through checking preflight logs, Gate token context, and store configuration in the correct order to identify the issue quickly.

Quick Start

Use the dev-debug-logs skill to find the root cause of a UI error you are seeing when running your FuseBase app locally with fusebase dev start.

Frequently Asked Questions about dev-debug-logs

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

FAQPage Schema
How do I debug local FuseBase app runtime logs when using the fusebase dev start CLI?▼

To debug local FuseBase app runtime logs, use symptom-based log routing to identify the correct log file for browser console errors, backend startup failures, or proxied API problems. This structured guidance helps you locate and interpret logs in seconds without manual searching.

Why does my FuseBase backend fail to start locally and which log file should I check?▼

If your FuseBase backend fails to start locally, check the backend startup failure logs using the symptom-based log routing rules. This directs you to the specific log file corresponding to startup errors, reducing troubleshooting time by eliminating guesswork.

How do I correlate browser console errors with backend API request logs during local development?▼

Correlate browser console errors with backend API logs using shared request IDs. Cross-service log correlation rules link frontend errors to proxied API request and response records, allowing you to trace issues across the full stack during local FuseBase development.

What is the best way to fix CORS and PostgreSQL Gate flow failures without modifying app code?▼

The best way to fix CORS and PostgreSQL Gate flow failures is following the pre-built troubleshooting runbook. It provides a step-by-step guide to check preflight logs, Gate token context, and store configuration in the correct order to resolve issues quickly without code changes.

How do I troubleshoot proxied API request and response issues in a local FuseBase dev environment?▼

Troubleshoot proxied API request and response issues by using the dev-debug-logs skill to locate the correct runtime logs. It provides structured guidance on inspecting API logs and correlating them with frontend errors using shared request IDs to identify root causes.

Can I use this log debugging approach for frontend dev server build errors in FuseBase?▼

Yes, you can use this log debugging approach for frontend dev server build errors in FuseBase. The symptom-based log routing rules clearly direct you to the specific log file needed to inspect and resolve frontend build problems during local testing.

Related Skills

Explore More Software Engineering Skills→
connectwithprakashconnectwithprakash

Python Project Setup with uv

Set up Python projects with uv for dependency management and environment configuration.

Community
Advanced
okgoogle13okgoogle13
1

api-integration-test-scaffolder

Generate integration test scaffolds for frontend, backend, and Genkit flows.

Community
Intermediate
AgentientAgentient
2

distributed-tracing-context-propagation

Propagate W3C trace context across HTTP service boundaries.

Official
Advanced
terna-ccterna-cc

sentry-setup

Configure Sentry SDK and integrate Pino for automated log forwarding.

Official
Basic