메뉴
Parses raw error logs and produces a concise, prioritized summary of unique issues with root cause hints.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Runs a systematic checklist review on any code diff or file, covering correctness, security, performance, and readability.
Writes a high-quality CLAUDE.md, .cursorrules, or .windsurfrules file that gives a coding agent the right project context, conventions, and constraints to work effectively.
Designs an eval suite for an LLM agent or pipeline including success metrics, trajectory scoring, LLM-as-judge setup, and regression test cases.
Designs a hybrid retrieval pipeline combining dense vector search and BM25 sparse search with reciprocal rank fusion, and explains when to use each configuration.
Converts a workflow description into a LangGraph node/edge graph with typed state, conditional routing, and human-in-the-loop checkpoints.
Audits an AI application for unnecessary token spend and recommends prompt caching, model routing, and token reduction techniques to cut costs.
| name | Error Log Summarizer |
| description | Parses raw error logs and produces a concise, prioritized summary of unique issues with root cause hints. |
| category | coding |
| tags | ["logs","debugging","monitoring","errors"] |
| author | simplyutils |
This skill directs the agent to ingest raw error logs — from a server, application, CI pipeline, or any other source — and produce a structured, de-duplicated summary. It groups repeated errors, counts occurrences, identifies the most frequent and most severe issues, and provides a root cause hint for each unique error type. The output gives you a clear picture of what's actually wrong without needing to scroll through thousands of log lines.
Use this when you have a dump of logs from a production incident, a CI failure, an error monitoring alert, or a server that's behaving oddly.
Copy this file to .agents/skills/error-log-summarizer/SKILL.md in your project root.
Then ask:
Paste the raw logs directly into the message, or provide a file path if the logs are in the repo.
Add the instructions below to your .cursorrules or paste them into the Cursor AI pane, then paste your raw logs.
Paste the logs directly in your message and ask Codex to follow the instructions below.
When asked to summarize error logs, follow these steps:
Read through the entire log. For each line or entry, extract:
Group log entries that represent the same underlying error. Two entries are the same error if:
For variable parts of error messages (e.g., user IDs, file names), replace them with a placeholder like [USER_ID] or [FILE_PATH] to produce a canonical error signature.
Count occurrences of each unique error.
Rank the unique errors by a combination of:
For each unique error, analyze the message, source, and any available stack trace to produce a 1–2 sentence root cause hypothesis. This is a hint to guide investigation, not a definitive diagnosis.
## Error Log Summary
**Log window**: [Start timestamp] → [End timestamp] (or "timestamps not present")
**Total log lines analyzed**: N
**Unique error signatures**: N
**Total error occurrences**: N
---
### Top Issues (by priority)
#### 1. [Error signature]
- **Severity**: ERROR / FATAL / WARN
- **Occurrences**: N times
- **First seen**: [timestamp or "unknown"]
- **Last seen**: [timestamp or "unknown"]
- **Source**: `file.ts:line` or service name
- **Sample message**: `[Exact or representative log line]`
- **Root cause hint**: [1–2 sentences on likely cause]
- **Suggested next step**: [Where to look first — a specific file, a query to run, a config to check]
#### 2. ...
---
### Warnings (non-critical but worth noting)
| # | Signature | Occurrences | Source | Note |
|---|-----------|-------------|--------|------|
| 1 | `Deprecated API used: /v1/users` | 43 | `api/userController.ts` | Will break on next major version |
---
### Noise / Expected Errors
[List any errors that appear expected or benign, e.g., health check 404s, with a brief explanation of why they can be ignored]
After the per-error breakdown, note any cross-cutting patterns:
Input to Agent:
"Use the Error Log Summarizer skill on these logs:
2024-01-15 14:02:11 ERROR [OrderService] Cannot read property 'price' of undefined at processOrder (order.service.ts:87) 2024-01-15 14:02:12 ERROR [OrderService] Cannot read property 'price' of undefined at processOrder (order.service.ts:87) 2024-01-15 14:02:15 WARN [AuthService] JWT expiry within 5 minutes for user 4821 2024-01-15 14:02:18 ERROR [OrderService] Cannot read property 'price' of undefined at processOrder (order.service.ts:87) 2024-01-15 14:02:20 ERROR [PaymentService] Stripe API timeout after 30s (requestId: req_abc123) 2024-01-15 14:02:21 ERROR [PaymentService] Stripe API timeout after 30s (requestId: req_def456) 2024-01-15 14:02:25 FATAL [OrderService] Unhandled promise rejection: Cannot read property 'price' of undefined ```"
Output from Agent:
Error Log Summary
Log window: 2024-01-15 14:02:11 → 14:02:25 Total log lines analyzed: 7 Unique error signatures: 3 Total error occurrences: 6 (+ 1 warning)
Top Issues
1.
Cannot read property 'price' of undefined— OrderService
- Severity: FATAL (escalated from ERROR)
- Occurrences: 4 times
- Source:
order.service.ts:87- Root cause hint: A product object is
undefinedat the point wherepriceis accessed — likely a missing null-check after a database lookup or an item that was deleted from the catalog while still in an active cart.- Suggested next step: Inspect
order.service.ts:87and the function that populates the product before line 87. Add a null guard.2.
Stripe API timeout after 30s— PaymentService
- Severity: ERROR
- Occurrences: 2 times
- Root cause hint: Stripe API is not responding within the 30-second timeout — could be a Stripe outage, network issue, or an unusually large payload.
- Suggested next step: Check https://status.stripe.com for incidents. Review the Stripe request payload size and consider reducing the timeout threshold with a retry strategy.
message and level fields correctly.