Skip to content
TrustedSkillsbeta
Back to all skills

E2E Ci Debug

Listed
lgariv-dn·vlatest·testing

Automatically analyzes end-to-end CI failures, identifies root causes, and suggests remediation steps for faster debugging.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add lgariv-dn/frontend-skills --skill e2e-ci-debug -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

lgariv-dn

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: cli.github.com.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    cli.github.comundeclared

    What it found

    • skills/e2e-ci-debug/scripts/download-artifacts.sh:38contacts cli.github.com
      echo "Install it from: https://cli.github.com/"
    • skills/e2e-ci-debug/scripts/find-failing-job.sh:43contacts cli.github.com
      echo "Install it from: https://cli.github.com/"

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned lgariv-dn/frontend-skills at e1bff232d1.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
e1bff232d1
Manifest
skills/e2e-ci-debug/SKILL.md
Scanned
7 files, 2,244 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill assists in debugging end-to-end (E2E) Continuous Integration (CI) pipelines. It can analyze CI logs, identify failing tests, and suggest potential root causes based on the error messages and test execution context. The tool aims to speed up troubleshooting by providing targeted insights into E2E pipeline failures.

When to use it

  • Failed builds: When your automated E2E tests are consistently failing in your CI environment.
  • Difficult-to-reproduce issues: When errors only occur during the CI process and aren't easily replicated locally.
  • Time constraints: To quickly pinpoint the source of failures within a complex E2E test suite, reducing debugging time.
  • Large teams: To help developers unfamiliar with specific parts of the codebase understand and resolve E2E pipeline issues.

Key capabilities

  • CI log analysis
  • Failing test identification
  • Root cause suggestions based on error messages
  • Test execution context understanding

Example prompts

  • "Analyze the latest CI logs for the 'checkout' feature and tell me why the tests are failing."
  • "What is the most likely root cause of this E2E test failure: [paste error message here]?"
  • "Can you identify which tests failed in the last build and suggest potential reasons?"

Tips & gotchas

The skill's effectiveness depends on the quality and detail present in your CI logs. Ensure your CI configuration includes comprehensive logging to maximize its utility.