troubleshooter

Diagnose and fix Open Mercato app issues across modules, migrations, APIs, and UI.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/dominikpalatynski/test-ready-app --skill troubleshooter-dominikpalatynski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshooter
Source: https://github.com/dominikpalatynski/test-ready-app/tree/main/.ai/skills/troubleshooter
Command: npx skills add https://github.com/dominikpalatynski/test-ready-app --skill troubleshooter-dominikpalatynski

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Troubleshooter enables developers to rapidly diagnose and fix issues across Open Mercato standalone apps, spanning modules, migrations, API routes, and UI rendering.

Core Features & Use Cases

  • Systematic diagnostic flow to identify symptoms and probable causes.
  • Cross-layer troubleshooting for modules, entities, API routes, UI widgets, and builds.
  • Quick remediation steps for common failures and edge cases.

Quick Start

Run a structured diagnostic sequence to identify and repair root causes across modules, migrations, APIs, and UI.

Frequently Asked Questions about troubleshooter

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

FAQPage Schema
How do I troubleshoot Open Mercato build errors and broken UI widgets?

Troubleshoot Open Mercato build errors and UI widget failures by running a structured diagnostic sequence using yarn dev and yarn typecheck to identify root causes across modules, API routes, and frontend rendering. It applies a systematic diagnostic flow to pinpoint exact failures.

Why does my Open Mercato migration fail when running yarn db:migrate?

Migration failures during yarn db:migrate often stem from database schema mismatches or broken module wiring. Run yarn db:generate to sync schema changes first, then follow a deterministic diagnostic flow to isolate and repair the underlying database or entity configuration issue.

What is the best way to diagnose 404 errors in Open Mercato API routes?

The best way to diagnose 404 errors in Open Mercato API routes is executing a cross-layer troubleshooting flow that validates module wiring and API responses. Run yarn generate to rebuild route configurations and apply systematic diagnostics to trace the missing endpoint.

Can I use this diagnostic flow to fix issues across multiple Open Mercato modules?

Yes, you can fix issues across multiple Open Mercato modules using this cross-layer troubleshooting approach. It systematically checks module wiring, database schema, API responses, and frontend rendering to identify and repair root causes spanning the entire standalone app architecture.

What should I do if yarn typecheck fails after fixing Open Mercato module wiring?

If yarn typecheck fails after repairing Open Mercato module wiring, rerun the deterministic diagnostic flow to check for remaining entity schema mismatches or broken API responses. Run yarn generate and yarn db:generate sequentially to ensure all generated types align with the updated module configurations.