Jianshi AI DevOps Automation

Problem

DevOps work is often split across GitHub Actions, alerting tools, chat channels, and infrastructure scripts. Teams can struggle to answer: who handles a failed deployment, where alerts route, and how postmortems are recorded. This skill puts CI/CD, monitoring, incident management, and infrastructure operations into a shared workflow model.

How It Works

It organizes common n8n-style IT operations templates:
- CI/CD automation: handles workflow_run events from GitHub Actions and produces start, success, or failure deployment notifications.
- Monitoring and alerting: defines alert routing and templates, including mention_on_failure for responsible on-call targets.
- Incident management: supports incident workflows and postmortem templates for failure stage, impact, and recovery notes.
- Infrastructure and Kubernetes: covers server provisioning, scheduled maintenance, and Kubernetes workflow patterns.

Boundaries

The skill focuses on workflow design and templating. It should not automatically install dependencies, change system permissions, create persistent tasks, or execute downloaded content. For sending, publishing, deletion, payment, deployment, or other external writes, review targets and impact first. Commands and code are reference material by default; run them only when explicitly requested and the target scope is clear.