vigil-incident

Diagnose production incidents by analyzing logs, metrics, and traces to identify root cause.

69|8|Updated Mar 16, 2026

Search Tags:#rollback #logs #metrics #observability #postmortem #root-cause #incident

Ready to run

npx skills add https://github.com/tonone-ai/tonone --skill vigil-incident

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vigil-incident
Source: https://github.com/tonone-ai/tonone/tree/main/team/vigil/skills/vigil-incident
Command: npx skills add https://github.com/tonone-ai/tonone --skill vigil-incident

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Incident response — diagnose production issues, find root cause, propose fix with rollback.

Core Features & Use Cases

Environment detection and symptom gathering to identify impacted services and configurations.
Log, metrics, and trace analysis to locate the root cause and assess blast radius.
Rollback planning and runbook generation to enable safe remediation and post-incident documentation.

Quick Start

Follow the incident response protocol by gathering logs, metrics, and traces, then identify root cause and outline a safe rollback plan.

Frequently Asked Questions about vigil-incident

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

FAQPage Schema

How do I diagnose a production incident by collecting logs, metrics, and traces?▼

To diagnose a production incident, you collect logs, metrics, and traces to identify the root cause. This process involves environment detection, symptom gathering, and reviewing observability data to assess the blast radius across impacted services.

What is the best way to plan a rollback after identifying a root cause?▼

The best way to plan a rollback is to determine the root cause through trace analysis and then generate a safe rollback plan. This includes creating runbooks for remediation and documenting the incident response steps for post-incident review.

How does root-cause analysis work across services, deployments, and infrastructure?▼

Root-cause analysis works by gathering symptoms and detecting environment configurations to locate impacted services. It correlates logs, metrics, and traces across deployments and infrastructure to pinpoint the exact failure point.

Can I use incident response runbooks to guide postmortem documentation?▼

Yes, you can use incident response runbooks to guide postmortem documentation. The process generates post-incident documentation that outlines the root cause, rollback planning, and remediation steps taken during the production incident.

What steps are needed to assess blast radius during an incident?▼

To assess blast radius, you perform environment detection and symptom gathering to identify impacted services. Log analysis, metrics review, and trace tracing are then applied to evaluate the extent of the failure across your infrastructure.