log-audit

Analyze Railway, file, and console logs for errors and patterns.

1|2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill log-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: log-audit
Source: https://github.com/parisgroup-ai/imersao-ia-setup/tree/main/skills/log-audit
Command: npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill log-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Logs often hide failure patterns and health signals; this skill analyzes multiple sources to extract actionable insights.

Core Features & Use Cases

  • Automated log parsing from Railway, files, and console
  • Pattern detection, health metrics, and PII checks with auto-reporting
  • Use cases include production incidents, compliance audits, and ongoing health monitoring

Quick Start

Run the log-audit across the last 6 hours to reveal critical issues and suggested tasks.

Frequently Asked Questions about log-audit

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

FAQPage Schema
How do I analyze Railway logs to identify recurring error patterns?

Analyzing Railway logs for recurring error patterns involves structured parsing and severity scoring to extract actionable health insights and generate automated reports. The process evaluates logs from Railway, files, and console outputs to detect failure patterns.

Can I detect PII in console outputs and log files during an audit?

Detecting PII in console outputs and log files during an audit is supported through enforced PII detection checks across Railway logs, files, and console outputs to support compliance audits and ensure sensitive data is identified.

What is the best way to generate a health report from production incident logs?

The best way to generate a health report from production incident logs is by applying pattern detection and severity scoring to the log data, producing health reports, timelines, and suggested tasks from Railway and console log sources.

Does automated log parsing support custom report generation for specific timeframes?

Automated log parsing supports custom report generation for specific timeframes through optional report customization, allowing you to run audits across defined periods, such as the last 6 hours, to reveal critical issues and produce tailored health metrics.

Why do I need severity scoring when monitoring application logs?

Severity scoring is needed when monitoring application logs to prioritize identified errors and recurring patterns effectively, enabling the system to distinguish critical issues from minor anomalies and directly informing the generated health reports and suggested tasks.