review-logs

Review Deus system health logs and rotate old files with Ollama.

50|4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/sliamh11/Deus --skill review-logs-sliamh11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-logs
Source: https://github.com/sliamh11/Deus/tree/main/.claude/skills/review-logs
Command: npx skills add https://github.com/sliamh11/Deus --skill review-logs-sliamh11

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Reviews Deus system health logs, surface pinned issues, and rotate old log files using a local Ollama model for structured health analysis.

Core Features & Use Cases

  • Automated health analysis of log streams with an Ollama model (default: gemma4:e4b)
  • Daily reports, pinned alerts, and rotation/archiving of old logs to prevent bloating
  • End-to-end workflow: log ingestion, health evaluation, issue pinning, and archival retention

Quick Start

Run python3 scripts/log_review.py to perform the full daily log health check.

Frequently Asked Questions about review-logs

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

FAQPage Schema
How do I automate daily log health analysis using a local model?

Automated log health analysis uses a local Ollama model to review system logs and surface issues. It evaluates daily log streams, pinning degraded alerts and identifying anomalies without external API dependencies.

What is the best way to rotate and archive old system logs to prevent bloating?

Log rotation and archival prevent bloating by moving old health logs to an archive based on configurable retention policies. This workflow manages log ingestion and archival automatically, ensuring long-term storage does not consume active disk space.

Do I need Ollama installed locally to run automated log reviews?

Yes, a local Ollama instance is required to perform automated log reviews. The Skill defaults to the gemma4:e4b model for structured health analysis, meaning you must have Ollama configured to ingest and evaluate log streams.

How does issue pinning work for degraded system health alerts?

Issue pinning surfaces and retains degraded system health alerts found during log review. The Ollama model analyzes daily logs, identifies degraded health states, and pins these specific issues for review before archiving the old logs.

Can I configure log retention policies for archived health logs?

Yes, log retention is configurable for the archival workflow. You can set retention policies to determine how long rotated health logs remain in the archive, managing end-to-end ingestion and archival to prevent bloating.

What is the process to run a full daily log health check?

Running a full daily log health check involves executing the log review script. This triggers the local Ollama model to perform ingestion, health evaluation, issue pinning, and log rotation across the environment in one end-to-end workflow.