insforge-debug

Diagnose InsForge project issues via CLI logs and health checks.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Charla-UTP/note --skill insforge-debug-charla-utp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: insforge-debug
Source: https://github.com/Charla-UTP/note/tree/main/my-app/.qwen/skills/insforge-debug
Command: npx skills add https://github.com/Charla-UTP/note --skill insforge-debug-charla-utp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnosing problems in InsForge projects by guiding the diagnostic workflow and surfacing relevant logs and status, enabling rapid localization of root causes. It does not provide automated fixes; share the diagnostic output with developers or agents for repair decisions.

Core Features & Use Cases

  • Guided triage across frontend SDK, HTTP status anomalies, edge function failures, slow database queries, authentication/authorization issues, realtime channel problems, and backend slowdowns.
  • Executes the right diagnostic commands and surfaces comprehensive logs to pinpoint root causes.
  • Works across frontend and backend layers to produce actionable diagnostic output for remediation.

Quick Start

Run a health check and diagnostic workflow to collect logs and surface the primary failure source for the current InsForge project.

Frequently Asked Questions about insforge-debug

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

FAQPage Schema
How do I diagnose backend performance degradation and edge function failures in InsForge?

Diagnosing slow database queries and HTTP status anomalies involves executing the InsForge CLI diagnostic workflow to collect logs and check system health, producing a structured output that isolates the primary failure source across frontend and backend layers.

What is the best way to triage authentication and authorization problems in an InsForge project?

The best way to triage authentication and authorization problems is running a guided diagnostic workflow via the InsForge CLI, which surfaces relevant logs and health status to rapidly localize the root causes without applying automated fixes.

Can I use this to automatically fix frontend SDK errors and realtime channel issues?

You cannot use this to automatically fix frontend SDK errors or realtime channel issues, because it strictly performs diagnosis by surfacing logs and guiding triage commands. You must share the diagnostic output with developers for repair decisions.

Does this diagnostic workflow require the InsForge CLI to check for slow queries and HTTP anomalies?

Yes, this diagnostic workflow requires executing the InsForge CLI to collect logs, check health, and produce structured output for identifying root causes of slow queries, HTTP status anomalies, and other backend performance issues.

How do I start troubleshooting realtime channel issues using CLI diagnostics?

To start troubleshooting realtime channel issues, run the health check and diagnostic workflow via the InsForge CLI. This collects comprehensive logs across frontend and backend layers to surface the primary failure source for remediation.