log-analysis-tools
Fast log file analysis with lnav, multi-framework support (Laravel, CodeIgniter, React, Next.js), automatic log pruning, and 70-80% token savings vs reading entire logs
npx skills add majiayu000/claude-skill-registry --skill log-analysis-tools --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Log Analysis Tools Skill **Purpose**: Fast, efficient log file analysis with framework-aware patterns and intelligent pruning ## 🎨 **VISUAL OUTPUT FORMATTING** **CRITICAL: All log-analysis-tools output MUST use the colored-output formatter skill!** ```bash bash .claude/skills/colored-output/color.sh skill-header "log-analysis-tools" "Analyzing log files..." bash .claude/skills/colored-output/color.sh progress "" "Parsing Laravel logs" bash .claude/skills/colored-output/color.sh info "" "Found 15 errors in last 24h" bash .claude/skills/colored-output/color.sh success "" "Analysis complete" ``` --- ## 🎯 Multi-Framework Support ### Framework Detection & Log Locations | Framework | Log Location | Format | Auto-Detect | |-----------|--------------|--------|-------------| | **Laravel** | `storage/logs/laravel.log` | Laravel JSON/text | ✅ composer.json | | **CodeIgniter 4** | `writable/logs/*.log` | CI4 format | ✅ app/Config/ | | **CodeIgniter 3** | `application/logs/*.php` | CI3 format | ✅ application/config/ | | **Symfony** | `var/log/*.log` | Monolog format | ✅ composer.json | | **React (CRA)** | Browser console, no server logs | Client-side | ✅ package.json | | **Next.js** | `.nex
- 🎨 VISUAL OUTPUT FORMATTING
- 🎯 Multi-Framework Support
- Framework Detection & Log Locations
- Framework-Specific Patterns
- 🚀 Auto-Activation Triggers
- 🖥️ Platform Compatibility
- Supported Platforms
- Required Dependencies
- Optional Dependencies (Enhanced Features)
- Tool Availability by Platform
- Graceful Fallback Chain
- Dependency Checking
- Performance Impact
- 📊 Commands
bash .claude/skills/colored-output/color.sh skill-header "log-analysis-tools" "Analyzing log files..." bash .claude/skills/colored-output/color.sh progress "" "Parsing Laravel logs" bash .claude/skills/colored-output/color.sh info "" "Found 15 errors in last 24h" bash .claude/skills/colored-output/color.sh success "" "Analysis complete" Install all tools (recommended) brew install lnav fd ripgrep bat Or install individually brew install lnav # Advanced log viewer brew install fd # Fast file finding brew install ripgrep # Fast text search
What does the log-analysis-tools skill do?
Fast log file analysis with lnav, multi-framework support (Laravel, CodeIgniter, React, Next.js), automatic log pruning, and 70-80% token savings vs reading entire logs
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill log-analysis-tools --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
