check-ci
Diagnose CI failures by inspecting GitHub Actions run logs, identifying root causes, and suggesting fixes. Use when CI is failing, a workflow run failed, checks are red, or the user asks "why is CI failing" or "fix CI".
What this skill does
# Check CI Diagnose GitHub Actions CI failures, identify root causes, and suggest targeted fixes. ## Prerequisites - The `gh` CLI must be authenticated (`gh auth status`) - The repository must have GitHub Actions workflows ## Step 1 — Identify the failing run Check the most recent workflow runs: ```bash gh run list --limit 5 ``` If the user provided a specific run ID or PR number, use that directly: ```bash gh run view <run-id> gh pr checks <pr-number> ``` If multiple workflows exist, ask the user which one to investigate, or check all failed ones. ## Step 2 — Get failure details For the failing run, get the detailed log: ```bash gh run view <run-id> --log-failed ``` This shows only the log output from failed steps. Parse the output to identify: - **Which step failed** (e.g., "Run checks", "Run make check") - **The specific error message** (e.g., biome format diff, lint error, test failure) - **The failing file(s) and line(s)** if available ## Step 3 — Classify the failure Map the failure to one of these categories and suggest the appropriate fix: | Failure type | Indicators | Fix command | | --- | --- | --- | | Formatting | `biome format`, `Formatter would have printed`, diff output | `make format` | | Linting | `biome lint`, `lint error`, rule names | `make fix` | | Validation | `validate-marketplace.sh`, version mismatch, missing fields | Fix the specific field, then `make validate` | | Test failure | `go test`, `npm test`, assertion errors | Read the test, fix the code, re-run tests | | Build failure | `go build`, `npm run build`, compilation errors | Fix the source code | | Workflow config | YAML syntax, action version, missing setup step | Fix `.github/workflows/*.yml` | ## Step 4 — Apply the fix For auto-fixable issues (formatting, linting): ```bash make fix # Runs biome format --write and biome check --write make validate # Verifies marketplace consistency make check # Confirms all checks pass locally ``` For manual fixes (test failures, build errors, validation issues): 1. Explain what is wrong and where 2. Suggest the specific code change needed 3. After the fix, run `make check` to verify locally before committing ## Step 5 — Verify locally Always run the full check suite before committing: ```bash make check ``` This mirrors what CI runs and catches issues before pushing. ## Step 6 — Report Summarize: - What failed and why - What was fixed - Whether `make check` now passes locally - Remind the user to commit and push the fix ## Common patterns ### Biome formatting failures These are the most common CI failures in this repo. The fix is always: ```bash make format # auto-fix formatting make check # verify ``` ### Version mismatch If `validate-marketplace.sh` reports version mismatch between `plugin.json` and `marketplace.json`, update both files to the same version. ### Missing marketplace entry If a new plugin directory exists but is not in `marketplace.json`, add the entry. Use `make validate` to check. ## Cross-plugin synergy - [ci-workflow](../ci-workflow/) — Generate CI workflows that this skill diagnoses - [makefile-workflow](../../makefile-workflow/) — Create the Makefile targets that CI calls
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.