github-actions-incident-timeline-auditCluster failed GitHub Actions runs into incident windows by repo to expose outage duration, impact scope, and escalation severity.
Install via ClawdBot CLI:
clawdbot install daniellummis/github-actions-incident-timeline-auditGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Mar 21, 2026
Engineering teams at SaaS companies can use this skill to automatically cluster failed GitHub Actions runs into incident windows during post-mortem analysis. This helps quantify outage duration and impact scope across microservices when CI pipelines fail, enabling faster root cause identification and reliability improvement prioritization.
Financial institutions with strict compliance requirements can audit their CI/CD pipeline failures over time to demonstrate operational resilience monitoring. The skill's ability to filter by repository and workflow patterns helps isolate incidents in regulated components while maintaining audit trails of failure patterns and escalation severity.
Platform engineering teams in large enterprises can run this skill periodically to generate JSON outputs for CI reliability dashboards. By setting FAIL_ON_CRITICAL=1, they can create automated gates that alert when critical incident thresholds are breached across hundreds of development teams sharing centralized GitHub Actions infrastructure.
Maintainers of popular open source projects can use the bundled fixtures feature to test incident detection logic before applying it to production runs. The regex filtering capabilities help distinguish between flaky tests in experimental branches versus actual production deployment failures that require immediate attention.
E-commerce engineering teams can correlate CI pipeline failures with traffic spikes during sales events. By adjusting INCIDENT_GAP_MINUTES and duration thresholds, they can identify whether deployment failures during peak loads create extended service degradation versus isolated, quickly-recovered incidents.
SaaS companies offering CI/CD monitoring platforms can bundle this skill as a value-added feature for enterprise customers. The JSON output format enables easy integration into existing dashboard systems, while the fail-gate functionality provides immediate operational alerts for premium support tiers.
DevOps consulting firms can use this skill during client engagements to analyze historical CI failure patterns and recommend infrastructure improvements. The ability to export both human-readable and machine-readable outputs supports both executive presentations and technical implementation plans.
GitHub Enterprise support providers can include this skill in premium support packages to help clients monitor CI reliability trends. The configurable thresholds allow customization for different organizational risk tolerances, making it valuable for compliance-driven industries with strict uptime requirements.
💬 Integration Tip
Pre-process GitHub Actions run data using the provided gh command example to ensure proper JSON formatting before running the audit script. Store output JSON in a time-series database for trend analysis across multiple audit periods.
Scored Apr 19, 2026
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Essential Git commands and workflows for version control, branching, and collaboration.
通过网页抓取获取 GitHub 按日/周/月增长的热门仓库。当用户询问 GitHub 趋势、热门项目、本周热点或「什么在 GitHub 上 trending」时使用。可输出列表或 JSON,无需 API Key。
GitHub 操作技能 - 创建仓库、推送代码、管理 Release。全自动,无需用户干预。
Semantic git history search and code archaeology. Use when asked why code exists, who owns a file, what introduced a regression, what changed in a commit ran...
Deep-dive analysis of GitHub projects. Use when the user mentions a GitHub repo/project name and wants to understand it — triggered by phrases like "帮我看看这个项目...