agentleFS
MongoDBKnown publishermongodb/mongodb-atlas-kubernetes/.claude/skills/investigate-e2e-failure/SKILL.md

investigate-e2e-failure

Skill201 starsChanged 9 months agoApache-2.0View on GitHub

This gives instructions on how to investigate end-to-end test failures.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check if the gh binary is installed.

    line 12
  2. Distinctive:

    Use the following command to get an overview about the failure:

    line 20
  3. Distinctive:

    Use the following command to download the logs for the failed job:

    line 56
  4. Distinctive:

    Look for error messages, stack traces, or any other indicators of what went wrong.

    line 64
  5. Distinctive:

    Check for any recent changes in the codebase that might have introduced the failure.

    line 65
  6. Distinctive:

    If necessary, reproduce the failure locally to gain a deeper understanding.

    line 66
  7. Distinctive:

    Document your findings and suggest potential fixes or improvements to prevent similar failures in the future.

    line 67

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

When to Use

Whenever the user asks "investigate the e2e failure 123", execute the instructions below.

Prerequisites

Check if the gh binary is installed.

Instructions

Download the overview

In order to prevent TLS issues, just execute gh with full permissions.

  1. Use the following command to get an overview about the failure:
$ gh run view --job 123

X main Test · 19282487500
Triggered via schedule about 2 months ago

X cloud-tests / e2e-tests / e2e (v1.34.0-kind, encryption-at-rest) in 10m48s (ID 123)
  ✓ Set up job
  ✓ Run actions/checkout@v5
  ✓ Install devbox
  ✓ Generate kustomized all-in-one install configs
  ✓ Extract k8s version/platform
  X Run CI E2E tests
  ✓ Upload logs on failure
  ✓ Post Install devbox
  ✓ Post Run actions/checkout@v5
  ✓ Complete job

ANNOTATIONS
! No files were found with the provided path: output/**. No artifacts will be uploaded.
cloud-tests / e2e-tests / e2e (v1.34.0-kind, encryption-at-rest): .github#20

X Process completed with exit code 2.
cloud-tests / e2e-tests / e2e (v1.34.0-kind, encryption-at-rest): .github#2510


To see the logs for the failed steps, try: gh run view --log-failed --job=123
View this run on GitHub: https://github.com/mongodb/mongodb-atlas-kubernetes/actions/runs/19282487500

Find the corresponding e2e test

In this example we see that a test in test/e2e with the label "encryption-at-rest" failed. In this case it is the test defined in test/e2e/encryption_at_rest/encryption_at_rest_test.go.

Analyze the failure

Use the following command to download the logs for the failed job:

$ gh run view --job 123 --log

Investigate

  1. Correlate the logs with the test code to identify the root cause of the failure.
  2. Look for error messages, stack traces, or any other indicators of what went wrong.
  3. Check for any recent changes in the codebase that might have introduced the failure.
  4. If necessary, reproduce the failure locally to gain a deeper understanding.
  5. Document your findings and suggest potential fixes or improvements to prevent similar failures in the future.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.