troubleshooter

Diagnose and fix Open Mercato standalone app issues with guided commands.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/TomekNocon/open-logistico --skill troubleshooter-tomeknocon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshooter
Source: https://github.com/TomekNocon/open-logistico/tree/main/packages/create-app/agentic/shared/ai/skills/troubleshooter
Command: npx skills add https://github.com/TomekNocon/open-logistico --skill troubleshooter-tomeknocon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnose and fix common issues in Open Mercato standalone apps. Use when encountering errors, unexpected behavior, modules not loading, widgets not appearing, migrations failing, build errors, or any "it doesn't work" situation. Triggers on "error", "not working", "broken", "fix", "debug", "why isn't", "can't", "fails", "crash", "missing", "404", "500", "module not found", "widget not showing".

Core Features & Use Cases

  • Diagnostic Framework: Follow a structured, step-by-step flow to identify the root causes of issues across modules, migrations, API routes, UI widgets, and builds.
  • Guided remediation: Provides concrete commands, checks, and rollback steps to restore functionality with minimal risk.
  • Real-world use case: When a module routes 404s or a build fails, use this skill to systematically diagnose and apply fixes.

Quick Start

Describe the problem symptoms and follow the diagnostic flow to identify and fix the issue in your Open Mercato app.

Frequently Asked Questions about troubleshooter

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

FAQPage Schema
How do I debug module loading errors and build failures in Open Mercato standalone apps?

To debug module loading errors and build failures in Open Mercato, follow a structured diagnostic flow that checks project error outputs and applies guided remediation commands like yarn generate and yarn dev to restore functionality.

What is the best way to diagnose a 404 error on a module route in an Open Mercato app?

The best way to diagnose a 404 error on an Open Mercato module route is to use a systematic diagnostic flow that traces module loading behavior and applies concrete checks to identify and resolve the routing failure.

Can I use a structured diagnostic flow to fix failing migrations in Open Mercato development environments?

Yes, you can fix failing migrations in Open Mercato by applying a structured diagnostic flow that identifies root causes across development environments and provides safe rollback steps to restore database functionality.

Does fixing widget visibility issues in Open Mercato require external data beyond project diagnostics?

No, fixing widget visibility issues in Open Mercato requires no external data beyond the project's own diagnostics commands and error outputs, relying entirely on guided remediation steps within your existing environment.

Why does my Open Mercato build crash, and how do I systematically identify the root cause?

Your Open Mercato build crashes due to failures across modules, API routes, or UI widgets, and you identify the root cause by following a step-by-step diagnostic flow that isolates the error output.

When should I use guided remediation instead of manually troubleshooting Open Mercato API and UI problems?

You should use guided remediation for Open Mercato API and UI problems when you encounter unexpected behavior or general failures, as it provides concrete commands and safe rollback steps to minimize risk.