agentleFS
Sign inStart free
dmzoneilldmzoneill/skills/check-integration-tests/SKILL.md

check-integration-tests

Skill2 starsChanged 19 days agoApache-2.0View on GitHub

Check Konflux integration test status and results. Lists test runs, gets results, shows snapshots. Use when user says "check integration tests", "integration test status".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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:

    No route to host → learn_tool_fix("konflux_list_integration_tests", "no route to host", "VPN not connected", "Run vpn_connect()")

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Check Integration Tests

Inputs

InputTypeDefaultPurpose
namespacestringaap-aa-tenantKonflux namespace
limitint10Number of results to show

Workflow

1. Bootstrap

  • persona_load("release") — konflux tools
  • check_known_issues("konflux", ""), check_known_issues("integration_test", "")
  • knowledge_query(project="automation-analytics-backend", persona="developer", section="gotchas")

2. List Tests

  • konflux_list_integration_tests(namespace="{namespace}")
  • Parse: passed, failed, running counts

3. Failed Test Details (if any failed)

  • konflux_get_test_results(name="{first_failed_test}", namespace="{namespace}")

4. Snapshots

  • konflux_list_snapshots(namespace="{namespace}")

5. Report

  • Summary: passed | failed | running | total
  • List recent test runs with status
  • Failed test details if failed > 0
  • Snapshot list
  • Log: memory_session_log("Checked integration tests", "namespace={ns}, tests={count}")

6. Failure Learning

  • Unauthorized → learn_tool_fix("konflux_list_integration_tests", "unauthorized", "K8s auth expired", "Run kube_login(cluster='konflux')")
  • No route to host → learn_tool_fix("konflux_list_integration_tests", "no route to host", "VPN not connected", "Run vpn_connect()")

Key MCP Tools

  • persona_load, konflux_list_integration_tests, konflux_get_test_results
  • konflux_list_snapshots, konflux_get_snapshot
  • check_known_issues, learn_tool_fix, knowledge_query, memory_session_log

Key Namespace

  • aap-aa-tenant — Konflux tenant for Automation Analytics

Useful Commands

konflux_get_test_results(name='<test-name>', namespace='aap-aa-tenant')
konflux_get_snapshot(name='<snapshot-name>', namespace='aap-aa-tenant')

Chains To

  • release_to_prod — if tests pass
  • ci_retry — if tests failed transiently
  • notify_team — notify of test results

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.

Check your setup, free