process-logs

Automate application error log processing and task delegation from database tables.

2|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/maslennikov-ig/MC-2 --skill process-logs-maslennikov-ig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: process-logs
Source: https://github.com/maslennikov-ig/MC-2/tree/main/.claude/skills/process-logs
Command: npx skills add https://github.com/maslennikov-ig/MC-2 --skill process-logs-maslennikov-ig

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the tedious process of monitoring application error logs, identifying root causes, and creating actionable tasks for developers, ensuring faster bug resolution and system stability.

Core Features & Use Cases

  • Automated Error Triage: Fetches new errors from error_logs and generation_trace tables.
  • Intelligent Routing: Assigns tasks to specialized subagents based on error complexity (DB, API, Types, UI).
  • Proactive Bug Fixing: Enforces strict bug-fixing principles, prioritizing root cause analysis and quality over speed.
  • Use Case: When a critical error appears in the production logs, this Skill automatically creates a high-priority bug ticket in Beads, assigns it to the appropriate specialist subagent, and tracks its resolution.

Quick Start

Process all new error logs from the system and create corresponding tasks.

Frequently Asked Questions about process-logs

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

FAQPage Schema
How do I automate error log processing from database tables?

Automating error log processing involves fetching new errors from tables like error_logs and generation_trace, categorizing them by complexity, and delegating tasks to specialized subagents for resolution. This ensures faster bug resolution and system stability.

How does intelligent routing work for bug tracking and task creation?

Intelligent routing for bug tracking assigns tasks based on error complexity, directing database issues to a database-architect subagent and frontend issues to a fullstack-nextjs-specialist. This ensures specialized bug fixing and proper task delegation.

Can I auto-mute known expected events in application error logs?

Yes, you can auto-mute known expected events in application error logs. The skill manages error statuses by automatically muting recognized events, allowing developers to focus only on unresolved and pending issues in the system.

What is the best way to enforce strict bug-fixing principles during task automation?

Enforcing strict bug-fixing principles during task automation requires prioritizing root cause analysis and code quality over speed. The skill proactively manages this by enforcing these standards when creating actionable tasks for specialized subagents.

Does this skill work with generation_trace and error_logs tables for debugging?

Yes, the skill directly fetches and processes new errors from both error_logs and generation_trace database tables. It categorizes these errors by environment and complexity to provide detailed reporting on resolved and pending issues.

Why are my application error logs not being categorized correctly for bug tracking?

Application error logs might not be categorized correctly if they lack sufficient complexity or environment data for the skill to parse. The skill intelligently categorizes errors by environment and complexity to properly route them to specialized subagents.