Log Analyze

Name: Log Analyze
Author: berkcangumusisik

ASecurity

Analyzes log output or a log file to find errors, patterns, and anomalies

10 stars
0 votes
0 copies
9 views
Added June 1, 2026

ai-agentsbashperformance

Security analysis

A100/100

Scanned June 1, 2026

npx -y skills add berkcangumusisik/claude-code-practices --skill log-analyze --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Log Analyze?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/berkcangumusisik-log-analyze/badge)](https://www.skillsdirectory.com/skills/berkcangumusisik-log-analyze)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: log-analyze
description: Analyzes log output or a log file to find errors, patterns, and anomalies
argument-hint: [log-file-path]
user-invocable: true
allowed-tools: Bash Read
effort: low
---

## Log Analysis

Source: **$1** (or read from stdin if not specified)

```bash
# If file provided
cat "$1" 2>/dev/null | tail -500

# Or last N lines of common log locations
tail -200 logs/app.log 2>/dev/null || journalctl -n 200 2>/dev/null
```

Analyze for:

### Errors & Exceptions
- Stack traces and their frequency
- Error codes and HTTP status patterns
- Repeated errors (same error > 3x = systemic issue)

### Performance Signals
- Slow requests (response time > 1s)
- Timeout patterns
- Memory/CPU warnings

### Anomalies
- Sudden spike in error rate
- Unusual request patterns (potential abuse)
- Auth failures in bulk

### Timeline
- When did errors start?
- Correlation with deployments or traffic spikes?

---

Produce a concise summary:
- **Root cause hypothesis** (most likely reason for issues)
- **Immediate action** (if critical)
- **Lines to investigate** (with context)