ci-triage
Investigate a failed GitHub Actions run or PR check, distinguish regression, flake, infrastructure and insufficient evidence, and reproduce with repository-owned gates and fixtures. Use for failed runs, red main or red PR checks.
- Installs
- 60
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/onsager-ai/dev-skills --skill ci-triage- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads ci-triage automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
CI triage
Scope
This skill owns evidence-based classification. The repo contract/overlay owns reproduction commands, expected failures, issue conventions and warning severity. Triage does not authorize code publication, reverts, issue/comments or mentions. Load pr-lifecycle when repair changes an authorized PR.
Prerequisites
Identify the run, workflow, exact tested SHA and event. For PRs distinguish the head from the tested merge preview. Use harness-operations when retrieving checks/logs requires a capability mapping. Authentication and log availability must be observed; do not assume all connectors expose the same fields or limitations.
Procedure
- Read run/job status, first failed step and bounded logs through the available GitHub tools. Redact credentials and personal data. If logs are unavailable, retain the status/configuration evidence and report the access limit.
- Compare the tested diff with the previous comparable run, including workflow, inputs, dependencies and environment. An earlier green commit alone does not establish a flake or prove causation. Identify a suspect change with evidence; do not blame an author from the merge-message shape alone.
- Reproduce in an authorized isolated checkout at the exact tested ref or merge result using its own gate commands and fixtures. Do not switch a parked primary checkout to the suspect branch. Browser failures use the repo's browser workflow; another product's routes or fixtures are not interchangeable.
- Classify with the following taxonomy. Missing logs, credentials, tooling or a reproducible environment limit confidence; report them rather than guessing.
- Follow the repo's issue convention only when authorized. If it uses a rolling main-red issue, search for an existing open tracker before creating one. Append concise evidence instead of opening duplicates. Do not notify people merely because a template contains a mention. Close a tracker only with authority and a cited green run for the affected workflow.
- For a repair, hand off to the repo workflow and pre-push/PR lifecycle. For a retry, retain the failed run and compare the same tested inputs. A green retry alone does not justify weakening a required assertion.
Classification
| Bucket | Evidence | Next action |
|---|---|---|
| regression | Deterministic failure tied to the tested change or its merged interaction | Reproduce and repair the demonstrated defect |
| flake | Same comparable inputs alternate outcomes, with evidence of a nondeterministic cause | Record/retry and address the cause |
| infra | Runner, service, network or dependency provisioning failed independently of product assertions | Repair/retry the environment |
| needs-human | Evidence or authority is insufficient for a reliable diagnosis | Gather available evidence; request any pending human decision through the structured question capability in harness-operations |
If a human must choose the next action or supply missing context, use the structured question capability in harness-operations, then wait before dependent work. A plain-text needs-human report alone does not request that decision when the tool is available. If unavailable, state the limitation and use the established handoff channel. Missing infrastructure alone does not require a human choice.
Completion
Report workflow/run URL, tested SHA, first failing step, bucket, confidence, reproduction result, bounded evidence and next action. A blocked reproduction is not a successful local check. Keep check status tied to the exact SHA.
FAQ
What does the ci-triage skill do?
Investigate a failed GitHub Actions run or PR check, distinguish regression, flake, infrastructure and insufficient evidence, and reproduce with repository-owned gates and fixtures. Use for failed runs, red main or red PR checks.
How do I install ci-triage?
Run npx skills add https://github.com/onsager-ai/dev-skills --skill ci-triage in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ci-triage/ (personal) or .claude/skills/ci-triage/ (project).
Which AI agents can use ci-triage?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is ci-triage safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains ci-triage?
It is published by onsager-ai in onsager-ai/dev-skills. It has 60 recorded installs.
More from onsager-ai/dev-skills
codegraph
onsager-ai/dev-skills
Pre-indexed code knowledge graph (MCP, SQLite + tree-sitter) for faster, lower-token exploration of brownfield codebases. Use when starting work on a repo larger than 500 files or when the task involves cross-file traversal — "where is X used", "what calls Y", "what breaks if I change Z", "trace flow from A to B", "explain this subsystem". Skip for single-file edits or sessions shorter than the cold-start cost. Triggers include "codegraph", "code graph", "index this repo", "where is X defined", "find callers of", "callees of", "blast radius of changing X", "explore this codebase". Cuts the grep + Read loops needed to orient, via O(1) SQLite lookups and FTS5 search over 8 MCP tools — but it's an unsound tree-sitter approximation, so grep stays the completeness backstop for renames/exhaustive callers.
github-integration
onsager-ai/dev-skills
Enable the GitHub CLI (gh) in Claude Code cloud sessions and GitHub Copilot coding agent environments. Use this skill when: (1) setting up a project so cloud AI agents can use gh for PRs, issues, and releases, (2) configuring setup scripts or SessionStart hooks for gh installation, (3) adding copilot-setup-steps.yml for GitHub Copilot agents, (4) troubleshooting gh auth failures in cloud sessions, or (5) configuring GHTOKEN for headless environments. Triggers on: "enable gh", "github integration", "Claude Code cloud setup", "copilot setup steps", "gh auth in cloud", "gh not working in cloud", "setup script", or any request involving GitHub CLI access from cloud-based AI coding agents.
git-commit
onsager-ai/dev-skills
Best practices for creating clean, atomic git commits with good messages. Use when: (1) staging and committing changes, (2) writing commit messages, (3) deciding what to group in a single commit, (4) handling pre-commit hook failures, (5) choosing between amend and new commit. Triggers on "commit", "stage", "git add", "write a commit message", or "commit my changes".
agent-browser
onsager-ai/dev-skills
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
web-testing
onsager-ai/dev-skills
L2 AI-driven web UI testing for a React/Vite dashboard app. Originally authored against the Onsager Dashboard (the body's route table + file paths are Onsager-shaped); other React dashboards fork the procedure and substitute their own routes / test paths. Use when testing UI on PRs, triaging L1 test failures, or verifying UI behavior at desktop + mobile viewports. Triggers include "test the UI", "check the dashboard", "triage L1 failure", "run L2 tests", "validate this PR", "exploratory test the web app".
rust-npm-publish
onsager-ai/dev-skills
Publish Rust binaries to npm using the optionalDependencies platform package pattern. Covers the full publish pipeline, version sync, workspace: protocol, and platform package architecture. Use when: (1) publishing Rust binaries to npm, (2) setting up the platform package pattern (main + per-OS packages), (3) debugging publish failures, (4) managing version sync across pnpm + Cargo workspaces, (5) working with workspace: protocol. Triggers on "publish", "platform packages", "optionalDependencies", "bin.js", "version sync", "workspace protocol", "npm tag", or "prepare-publish".
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.