What it does
Parses debug.log or the server PHP error log, groups repeated entries by file, line, and message pattern instead of listing every timestamped occurrence, and attributes each group to the plugin, theme, or core file responsible so the reader knows exactly where to look first.
Install
This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:
Use it in your AI assistant
Claude Code
.claude/skills/error-log-summarizer/ (or ~/.claude/skills/error-log-summarizer/ for all projects)
GitHub Copilot (VS Code)
.github/skills/error-log-summarizer/
OpenAI Codex
.codex/skills/error-log-summarizer/
Cursor
.cursor/skills/error-log-summarizer/ (or ~/.cursor/skills/error-log-summarizer/ globally)
Compatibility
Any WordPress site; needs read access to wp-content/debug.log or the hosting account's PHP error log.
The complete SKILL.md for this skill:
---
name: error-log-summarizer
description: Use when a user pastes a raw PHP error log or debug.log and wants to know what's actually wrong, or asks "what do these errors mean".
---
# Error Log Summarizer
## When to use
A user has a raw, noisy error log (often thousands of near-duplicate lines) and wants to understand what's actually broken without reading every entry themselves.
## Procedure
1. Parse the log into individual entries, capturing timestamp, error type (notice, warning, fatal), file, line, and message.
2. Group entries by matching file, line, and message pattern rather than listing duplicates separately, and count occurrences per group.
3. Attribute each group to the responsible plugin, theme, or core file based on the file path.
4. Rank groups by severity first (fatal errors before warnings before notices), then by frequency within each severity tier.
5. Write one plain-English sentence per group explaining what's likely happening and its probable impact (e.g. "breaks page load" vs. "cosmetic, ignorable").
6. End with a short prioritized action list, top 3 things to fix first, rather than a full re-listing of every group.
## Guardrails
- Do not include full stack traces, file paths, or database values that might contain sensitive data (API keys, user info) verbatim in the summary if the user is going to share it externally, warn them before they paste it elsewhere.
- Never guess at a fix and apply it directly, only diagnose; code changes need the user's review and testing.