jahia-dev-debug

Trace Jahia JavaScript module deployment failures using live Docker logs.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Jahia/formidable --skill jahia-dev-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jahia-dev-debug
Source: https://github.com/Jahia/formidable/tree/main/.agents/skills/jahia-dev-debug
Command: npx skills add https://github.com/Jahia/formidable --skill jahia-dev-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jahia modules may fail to load due to build, deployment, or runtime issues. This Skill guides you through end-to-end diagnosis from source to runtime using live Docker logs to identify the first failure and the root cause.

Core Features & Use Cases

  • End-to-end debugging of Jahia JS modules, from build to runtime.
  • Deterministic identification of the first error after deployment using container logs.
  • Guidance for reproducing, patching, and verifying fixes in a Docker-based Jahia environment.

Quick Start

Run the build, then deploy, and finally monitor Docker logs to reproduce and identify the first runtime error.

Frequently Asked Questions about jahia-dev-debug

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

FAQPage Schema
How do I debug a Jahia JavaScript module that fails to load after deployment?

To debug a Jahia JavaScript module load failure, trace the end-to-end deployment pipeline from source to runtime using live Docker logs to identify the first runtime error after running yarn build and yarn jahia-deploy.

Why does my Jahia module build succeed but fail at runtime?

A Jahia module may fail at runtime due to deployment or runtime issues not caught during build. Monitoring live Docker logs after deployment helps pinpoint the first runtime failure and its root cause.

What's the best way to troubleshoot Jahia module deployment issues in Docker?

The best way to troubleshoot Jahia module deployment issues in Docker is running the build, deploying with yarn jahia-deploy, and observing live Docker container logs to deterministically isolate the first failure.

Do I need access to the module source code to diagnose Jahia deployment failures?

Yes, diagnosing Jahia deployment failures requires access to the module's source code, Docker, and deployment tooling like yarn build and yarn jahia-deploy to reproduce, patch, and verify the fix.

How does tracing the deployment pipeline help fix Jahia module load errors?

Tracing the deployment pipeline isolates failures across build, deployment, and runtime stages. This deterministic approach identifies the exact first error in the process, enabling targeted patching and verification in a Docker environment.