skills.rest
ChazzCoin
ChazzCoinCOMMUNITY
Explore all skills by this author →
GitHub

incident

Manage cross-stack incident lifecycles with markdown and filesystem operations.

Updated May 7, 2026
Search Tags:#audit#postmortem#incident management#cross-stack#resolution tracking
One-click install
npx skills add https://github.com/ChazzCoin/claude-orchestrator --skill incident-chazzcoin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incident
Source: https://github.com/ChazzCoin/claude-orchestrator/tree/main/kit/skills/incident
Command: npx skills add https://github.com/ChazzCoin/claude-orchestrator --skill incident-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive system for tracking, resolving, and documenting cross-stack incidents, ensuring timely and effective responses.

Core Features & Use Cases

  • Cross-Stack Incident Management: Track and resolve incidents affecting multiple sub-repositories or with cross-cutting implications.
  • Incident Creation: Open a new incident, update existing ones, and prepare postmortems.
  • Timeline Tracking: Monitor incident statuses and timelines through chronological entries.
  • Postmortem Creation: Document the root causes and resolutions, including actionable items.
  • Automated Auditing: Generate AUDIT entries to keep a historical record of incident resolutions.
  • Use Case: If a major system-wide outage occurs, quickly open an incident, update the timeline with relevant information, prepare a postmortem, and file necessary action items to prevent recurrence.

Quick Start

Use the incident skill to create a new incident report and begin the troubleshooting process with the command 'incident open <summary>'.

Frequently Asked Questions about incident

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

FAQPage Schema
How do I manage cross-stack incidents across multiple software repositories?▼

Cross-stack incident management tracks incidents affecting multiple sub-repositories through creation, timeline updates, and resolution phases. It facilitates detailed incident reports, captures root causes, and tracks follow-up actions for system recovery.

What's the best way to document root causes and resolutions for a major system outage?▼

Documenting root causes and resolutions for a major system outage requires generating detailed incident reports and postmortems. This process captures actionable items and generates AUDIT entries to keep a historical record of incident resolutions for future prevention.

How do I track incident status and timeline entries during troubleshooting?▼

Tracking incident status and timeline entries involves monitoring chronological updates throughout the incident lifecycle. You can open a new incident, update existing ones with relevant information, and prepare postmortems to document the full resolution process.

Do I need markdown and filesystem operations to track incident lifecycles?▼

Yes, tracking incident lifecycles requires markdown and filesystem operations to store incident reports, timeline entries, and postmortems. These operations enable the creation, update, and resolution phases of cross-stack incidents across multiple software repositories.

Can I generate automated audit entries for historical incident resolution records?▼

Yes, you can generate automated AUDIT entries to keep a historical record of incident resolutions. This feature operates alongside postmortem creation to document root causes, resolutions, and actionable items for system recovery and improvement.

Related Skills

Explore More Software Engineering Skills→
incidentfoxincidentfox
654

project-clickup

Automate ClickUp incident tracking and task management via HTTP API.

Official
Basic
arch-teamarch-team
73

pace-feedback

Collect user feedback, classify production incidents, and generate postmortems.

Community
Advanced
FoundationForgeFoundationForge

incident-response

Manage incident response workflows for production outages and alerts.

Official
Advanced
sun2443sun2443

incident-response

Manages incident response workflows from detection through postmortem documentation.

Community
Intermediate