skills.rest
confighub
confighubOFFICIAL
Explore all skills by this author →
WebsiteGitHub

incident-management

Coordinates ConfigHub incident triage and routes to mutation or reconciliation tasks via kubectl and cub tooling.

2|2|Updated Apr 15, 2026
Search Tags:#rollback#kubectl#triage#incident-management#confighub#cub#drift-reconcile
One-click install
npx skills add https://github.com/confighub/confighub-skills --skill incident-management-confighub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incident-management
Source: https://github.com/confighub/confighub-skills/tree/main/skills/incident-management
Command: npx skills add https://github.com/confighub/confighub-skills --skill incident-management-confighub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrator for the ConfigHub-side of a production incident. Triages, decides stabilize vs rollback vs reconcile, and hands off to the mutating skill that will do the actual work. Does not mutate itself.

Core Features & Use Cases

  • Structured incident triage with a decision path that routes to rollback-revision, cub-mutate, cub-apply, drift-reconcile, or verify-apply based on the symptom.
  • Clear change-desc logging for every mutation to support postmortems and audits.
  • Post-incident close-out guidance, including tagging revisions and verifying green state.

Quick Start

Operate by stating the incident and selecting the appropriate path (rollback, mitigate, or reconcile) to hand off to the corresponding skill with a clear change-desc.

Frequently Asked Questions about incident-management

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

FAQPage Schema
How do I triage a production incident to decide between rollback or drift reconciliation?▼

Production incident triage evaluates symptoms to route decisions toward stabilize, rollback, or drift reconciliation. It coordinates targeted mitigation across Units and Changesets, handing off to the appropriate mutation skill based on the specific failure.

What's the best way to structure a fast rollback during an active incident?▼

Structured rollback during active incidents routes to rollback-revision for execution. The triage process ensures rollback decisions include clear change-desc logging to support postmortems and consistent state verification.

Do I need kubectl and cub tooling to perform ConfigHub incident triage?▼

Yes, cub and kubectl tooling are required dependencies for ConfigHub incident triage. These tools enable the orchestration of drift reconciliation, mutation handoffs, and verification across Units and Changesets.

Why does incident triage require a change-desc for every configuration mutation?▼

Incident triage requires change-desc for every mutation to enforce audit trails and support postmortems. Logging all changes ensures that rollback, mitigation, and reconciliation actions are traceable across active production environments.

Can this incident triage process apply mutations directly to resolve the issue?▼

No, incident triage orchestrates the decision path but does not mutate configurations directly. It hands off to specialized skills like cub-mutate, cub-apply, or drift-reconcile to execute the actual remediation work.

Related Skills

Explore More Software Engineering Skills→
confighubconfighub
2

import-from-helm

Render Helm charts into ConfigHub Units and manage upgrades with cub.

Official
Intermediate
oalansilvaoalansilva

incident-postmortem

Draft incident postmortems with timeline, RCA, and action items.

Community
Intermediate
confighubconfighub
2

rollback-revision

Roll back a Unit's head to a prior revision using cub unit update --restore.

Official
Advanced
ConductionNLConductionNL

app-verify

Audit Nextcloud app files against openspec/app-config.json to detect drift.

Official
Intermediate