troubleshooter

Diagnose and resolve Open Mercato standalone app issues with systematic fixes.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/comerito/om-hackathon-starter --skill troubleshooter-comerito
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshooter
Source: https://github.com/comerito/om-hackathon-starter/tree/main/.ai/skills/troubleshooter
Command: npx skills add https://github.com/comerito/om-hackathon-starter --skill troubleshooter-comerito

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnose and fix common issues in Open Mercato standalone apps. When developers encounter errors, unexpected behavior, or modules not loading, this skill provides a structured approach to identify symptoms, verify causes, and apply fixes.

Core Features & Use Cases

  • Systematic diagnostic flow that guides troubleshooting across modules, entities, API routes, UI, and builds.
  • Quick verification steps such as regenerating discovery files and restarting the dev server to fix common issues.
  • Clear, step-by-step guidance for common pain points including 404/module not found errors, migrations, and widget visibility.

Quick Start

Describe the exact error and steps to reproduce to begin the diagnostic flow.

Frequently Asked Questions about troubleshooter

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

FAQPage Schema
How do I fix Open Mercato standalone app build errors and module not found issues?

To fix Open Mercato build errors and module not found issues, follow a systematic diagnostic flow to identify symptoms and apply fixes. Quick verification steps include regenerating discovery files with yarn generate and restarting the dev server with yarn dev to resolve common loading failures.

What is the best way to troubleshoot Open Mercato widgets not loading?

Troubleshooting Open Mercato widgets not loading involves a structured diagnostic approach across UI layers. Guide systematic fixes by first regenerating discovery files and restarting the dev server, which often resolves widget visibility issues and API route misbehaviors.

How do I resolve database migration failures in Open Mercato standalone apps?

Resolving database migration failures in Open Mercato standalone apps requires identifying symptoms and verifying causes across the database layer. The diagnostic flow provides step-by-step guidance to systematically fix migrations and apply safe defaults.

Does the Open Mercato diagnostic flow work for API route and runtime failures?

Yes, the Open Mercato diagnostic flow works for API route and runtime failures by guiding systematic fixes across module and API layers. It applies safe defaults and uses standard commands like yarn dev to verify causes and restore expected behavior.

What should I do when Open Mercato modules misbehave after a build?

When Open Mercato modules misbehave after a build, describe the exact error and steps to reproduce to begin the diagnostic flow. Regenerating discovery files and restarting the dev server serve as quick verification steps to fix unexpected behavior.