om-troubleshooter

Name: om-troubleshooter
Availability: InStock
Author: SHGrowth

Diagnose and fix common Open Mercato standalone app issues with systematic checks.

6|2|Updated Mar 27, 2026

Search Tags:#debugging #troubleshooting #migration #diagnostics #build-errors #module-loading #open-mercato

Ready to run

npx skills add https://github.com/SHGrowth/om-superpowers --skill om-troubleshooter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: om-troubleshooter
Source: https://github.com/SHGrowth/om-superpowers/tree/main/skills/om-troubleshooter
Command: npx skills add https://github.com/SHGrowth/om-superpowers --skill om-troubleshooter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnoses and fixes common issues in Open Mercato standalone apps, enabling developers to quickly identify root causes when errors, misbehaving modules, missing widgets, migrations failures, or build errors occur.

Core Features & Use Cases

Systematic diagnostic flow to identify the symptom layer and potential causes across modules, entities, APIs, UI, and builds.
Guided, step-by-step commands and checks to regenerate module discovery, verify routing, migrate databases, and validate UI components.
Unified playbook for rapid incident response in development and staging environments, with clear remediation paths and rollback guidance.

Quick Start

Run the Troubleshooter on your Open Mercato project to identify the issue category and apply the recommended fixes.

Frequently Asked Questions about om-troubleshooter

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

FAQPage Schema

How do I fix Open Mercato build errors when modules are not loading?▼

Open Mercato build errors and module loading failures are resolved by regenerating module discovery and validating API routes through a systematic diagnostic flow. It applies guided checks to identify the symptom layer across modules, entities, APIs, and UI components, providing clear remediation steps.

Why does my Open Mercato migration fail and how do I apply fixes?▼

Open Mercato migration failures are diagnosed by following a structured set of checks to verify database state and apply migrations correctly. The troubleshooting playbook identifies the specific failure point within your development environment and provides step-by-step remediation commands with rollback guidance.

What is the best way to troubleshoot missing widgets in Open Mercato standalone apps?▼

Troubleshooting missing widgets in Open Mercato standalone apps is best handled by a unified diagnostic playbook that validates UI components and verifies routing. It systematically identifies whether the issue stems from module discovery, API routes, or UI layer misconfiguration.

Can I use this diagnostics flow for Open Mercato staging environments?▼

Yes, the diagnostics flow works for Open Mercato staging environments as a unified playbook for rapid incident response. It applies systematic checks and remediation paths to identify root causes for errors, unexpected behavior, and build issues across both development and staging setups.

How do I validate API routes when troubleshooting Open Mercato app errors?▼

Validating API routes during Open Mercato troubleshooting involves running guided, step-by-step checks to verify endpoint configuration and connectivity. This diagnostic step isolates whether unexpected behavior or module errors originate from routing misconfigurations or deeper build and migration issues.