ci-log-interpretation

Included with Lifetime

$97 forever

Use this skill when reading or analyzing CI logs from a Shopware GitHub Actions workflow to figure out why a build failed — phrases like "why did CI fail", "what broke the build", "check the pipeline", "interpret these logs", "debug this red build" — or whenever raw run logs, job logs, or check annotations from a failed GitHub Actions workflow appear in the conversation. Covers PHPUnit, PHPStan, ECS, ESLint, TypeScript, Stylelint, Prettier, Jest, Playwright, ludtwig, and Lighthouse failures. Activate even if the user does not explicitly mention "CI" — any interaction with GitHub Actions failure output benefits from this skill's noise-filtering and tool-identification knowledge.

Cloud & DevOps

What this skill does


# CI Log Interpretation

## Job Name → Tool Mapping

| Job name pattern | Tool |
|---|---|
| `PHPUnit` | PHPUnit |
| `PHP analysis` / `PHPStan` | PHPStan |
| `PHP lint` / `ECS` / `php-cs-fixer` | ECS |
| `lint` (in admin/storefront workflow) | ESLint, tsc, Stylelint, or Prettier |
| `Jest` / `unit` (JS context) | Jest |
| `acceptance` / `Playwright` | Playwright |
| `Lighthouse` | Lighthouse |
| `Twig Lint` / `ludtwig` | ludtwig |

## Output Signatures

When the job name is ambiguous, identify the tool from its output:

| Signature in log | Tool |
|---|---|
| `There was 1 failure:` or `There were N errors:` | PHPUnit |
| `[ERROR] Found N errors` | PHPStan |
| `Found N of M files that can be fixed` | ECS |
| `✖ N problems (N errors, N warnings)` | ESLint |
| `error TS` followed by 4-digit code | TypeScript (tsc) |
| `✖ N problems` in SCSS context | Stylelint |
| `Code style issues found` | Prettier |
| `● suite-name › test-name` | Jest |
| `expect(locator).toXxx() failed` | Playwright |
| `Assertion failed. Exiting with status code 1.` | Lighthouse |
| `error[RuleName]:` | ludtwig |

## Universal Noise (Never the Root Cause)

These patterns appear in ALL GitHub Actions logs and are never the actual error:

- **Timestamp prefix**: Every line starts with `YYYY-MM-DDTHH:MM:SS.NNNNNNNZ` — ignore it
- **Step boundaries**: `##[group]Step Name` / `##[endgroup]` — structural, not errors
- **Step exit marker**: `##[error]Process completed with exit code N.` — ALWAYS the last line of a failed step. This is the step exit marker, NOT the actual error. Never report this as the root cause.
- **Setup noise**: checkout, Docker pulls, `actions/cache`, composer install, npm install, tool downloads
- **Post-job noise**: cache saving, git config cleanup, orphan process termination
- **Infrastructure noise**: `npm error command failed`, `socket hang up`, `ECONNREFUSED` — CI environment issues, not code errors (exception: for Playwright these CAN be the actual cause)

For detailed GitHub Actions log format knowledge, see `references/log-envelope.md`.

## Tool-Specific References

Detailed failure anatomy, output format, false positives, and real examples for each tool:

| Tool(s) | Reference |
|---|---|
| PHPUnit, PHPStan, ECS | `references/php-tools.md` |
| ESLint, tsc, Stylelint, Prettier, Jest | `references/js-tools.md` |
| Playwright, Lighthouse, ludtwig | `references/e2e-tools.md` |

## What to Report

- The specific file(s) and line number(s) that caused the failure
- The error message in the tool's own words
- The rule or check that failed (if applicable)
- For diff-based tools (ECS, Prettier): the expected vs actual code

Files: 6

Size: 14.0 KB

Complexity: 43/100

Category: Cloud & DevOps

Source: https://github.com/shopwarelabs/ai-coding-tools/tree/main/plugins/ci-failure-interpretation/skills/ci-log-interpretation

Related in Cloud & DevOps

appbuilder-action-scaffolder

Included

Create, 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.

Cloud & DevOpsscripts

orchestrating-datacloud

Included

Salesforce 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).

Cloud & DevOpsscripts

github-project-automation

Included

Automate 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

Cloud & DevOpsscripts

sf-datacloud

Included

Salesforce 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).

Cloud & DevOpsscripts

fabric-cli

Included

Use 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.

Cloud & DevOpsscripts

lark

Included

Lark/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.

Cloud & DevOpsscripts