log-monitor

Analyze Laravel production logs to categorize errors and generate GitHub issues.

20|5|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/nasrulhazim/agent-skills --skill log-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: log-monitor
Source: https://github.com/nasrulhazim/agent-skills/tree/main/skills/log-monitor
Command: npx skills add https://github.com/nasrulhazim/agent-skills --skill log-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Laravel production logs trap errors and outages, but without structured triage and automation it is hard to prioritize fixes and keep stakeholders informed.

Core Features & Use Cases

  • Analyze Laravel log files to categorize errors by type and severity.
  • Generate daily reports and error-type summaries, then draft GitHub issues with proper labels and project board mapping.
  • Create actionable items and dashboards to monitor health across multiple repositories.

Quick Start

Provide your Laravel log directory to auto-generate error insights, issue drafts, and a project-ready triage plan.

Frequently Asked Questions about log-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze Laravel production logs to categorize errors by severity?

To triage Laravel production log errors, you provide your log files or directory to automatically categorize errors by type and assess severity. The tool then generates structured reports and drafts actionable GitHub issues with proper labels and project board integration.

Can I generate GitHub issues automatically from Laravel log files?

Yes, you can generate GitHub issues automatically from Laravel log files. The analysis drafts actionable issues with proper labels and project board mapping, converting raw production errors into structured development tasks.

Does this Laravel log triage process work with multi-project repositories?

Yes, Laravel log triage works with multi-project collections. It creates actionable items and dashboards to monitor health across multiple repositories, applying error categorization and severity assessment to single files, daily directories, or multi-project sets.

What is the best way to automate daily Laravel error reporting and triage?

The best way to automate daily Laravel error reporting is to process your log directory to generate daily reports and error-type summaries. This automated triage categorizes errors and drafts GitHub issues to keep stakeholders informed.

Are bilingual reporting and report templating supported for Laravel log analysis?

Yes, bilingual reporting and report templating are supported for Laravel log analysis. The process includes error categorization, severity assessment, and structured report templating to produce outputs in multiple languages.