skills.rest
CyanAutomation
CyanAutomationCOMMUNITY
Explore all skills by this author →
GitHub

ci-triage

Triages CI and security failures in GitHub Actions workflows.

1|Updated Jan 14, 2026
Search Tags:#automation#workflow#security#github-actions#triage#reproducibility#ci
One-click install
npx skills add https://github.com/CyanAutomation/motioninocean --skill ci-triage-cyanautomation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-triage
Source: https://github.com/CyanAutomation/motioninocean/tree/main/.github/skills/ci-triage
Command: npx skills add https://github.com/CyanAutomation/motioninocean --skill ci-triage-cyanautomation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CI failures and security-scan issues in GitHub Actions can be time-consuming to diagnose. This skill provides a repeatable triage playbook to speed up identification, reproduction, and closure.

Core Features & Use Cases

  • Global triage sequence that standardizes failure interpretation, reproduction, and escalation for ci.yml and security-scan.yml.
  • Fast local reproduction with Makefile targets and direct commands to parity CI results.
  • Structured closure templates and escalation guidance to hand off to infra or policy teams when needed.

Quick Start

Follow the triage playbook to reproduce the first failing job and apply the steps to diagnose and close the issue.

Frequently Asked Questions about ci-triage

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

FAQPage Schema
How do I triage GitHub Actions CI failures faster?▼

To triage GitHub Actions CI failures faster, apply a standardized triage sequence to interpret test, lint, and type-check errors in .github/workflows/ci.yml, then use Makefile targets to reproduce the failing jobs locally for rapid diagnosis.

What is the best way to reproduce security scan failures locally from GitHub Actions?▼

The best way to reproduce security scan failures locally is by using the provided Makefile targets and direct commands that mirror the .github/workflows/security-scan.yml environment, ensuring local parity with your CI results for faster remediation.

How do I standardize CI triage and escalation for my engineering team?▼

You can standardize CI triage and escalation by following a repeatable triage playbook that provides structured closure templates and escalation guidance to hand off unresolved issues to infra or policy teams.

Does this CI triage workflow support both test and security scan jobs?▼

Yes, this CI triage workflow supports both test and security scan jobs by specifically targeting the .github/workflows/ci.yml and .github/workflows/security-scan.yml files to standardize failure interpretation and remediation.

When should I use a structured triage playbook for CI failures?▼

You should use a structured triage playbook for CI failures when diagnosing test, lint, type-check, or security issues in GitHub Actions becomes time-consuming and requires repeatable local reproduction steps and formal closure templates.

Why does my GitHub Actions security scan fail locally but pass in CI?▼

GitHub Actions security scan failures that do not reproduce locally often indicate environment discrepancies; using the provided Makefile targets designed for local reproduction helps achieve parity with the .github/workflows/security-scan.yml environment to identify the mismatch.

Related Skills

Explore More Software Engineering Skills→
CyanAutomationCyanAutomation
1

ci-quality-gates

Reproduce CI quality gates locally to diagnose PR failures.

Community
Intermediate
aanishsaanishs
10

comply-fix

Identify and remediate failed HIPAA/NIST controls with automated patches and re-scans.

Community
Advanced
LuigiAPCPereiraLuigiAPCPereira

golang-continuous-integration

Automate Golang CI/CD with GitHub Actions for testing, linting, and releases.

Community
Advanced
saitarrunsaitarrun
4

cicd

Standardize CI/CD pipeline design and deployment workflows.

Community
Intermediate