drupal-debug

Diagnose recent errors in the Drupal project — watchdog entries, PHP errors, configuration problems, and container health.

Usage

/drupal-debug

What it checks

1. Watchdog errors

Shows the last 20 error and critical-level watchdog entries. Filters for actionable messages (skips routine info/notice entries).

2. PHP error log

Reads the PHP-FPM error log from the container for fatal errors, warnings, and deprecation notices that bypass watchdog.

3. Configuration sync state

Checks for pending configuration imports or exports:

drush config:status

Reports any configuration that is out of sync between the active store and the sync directory.

4. Container health

Checks all stack containers are running and reports any that are stopped, restarting, or in an error state.

5. File permission issues

Checks sites/default/files/ and private/ (if configured) for common permission problems that cause upload or cache write failures.

Interpreting results

The agent analyses the combined output and provides a prioritised list of issues with suggested fixes. For each issue it will either:

• Run a fix directly (e.g. drush cr for cache issues)
• Explain the cause and next steps
• Ask for more context if the error is ambiguous

Notes

• Use /drupal-debug as a first step when the site is broken or behaving unexpectedly.
• For ongoing log monitoring use /drupal-logs instead.

Related skills

• drupal-logs — watchdog log viewer with filters
• drupal-status — full project status report
• drupal-cr — rebuild caches (often fixes config-related errors)