agentleFS
Sign inStart free
dmzoneilldmzoneill/skills/check-ci-health/SKILL.md

check-ci-health

Skill2 starsChanged 21 days agoApache-2.0View on GitHub

Diagnose GitLab CI/CD pipeline issues. Use when user says "check CI", "pipeline status", "why is CI failing?", or "CI health". Lists pipelines, shows failing jobs, gets trace logs, validates .gitlab-ci.yml.

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:

    If failures detected: suggest or run skill_run("ci_retry", '{"project": "{{ project }}"}')

    line 41

≈ “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 CI Health

Diagnose GitLab CI/CD pipeline issues. Uses developer persona (gitlab tools).

Inputs

InputTypeDefaultPurpose
projectstringautomation-analytics/automation-analytics-backendGitLab project path
statusstringfailedFilter: failed, success, running, all
limitint5Number of pipelines to show
trigger_newboolfalseTrigger new pipeline run
branchstringmainBranch for trigger_new

Workflow

1. Load Persona

  • persona_load("developer")

2. List Pipelines

  • gitlab_ci_list(project="{{ project }}", status="{{ status }}")
  • Parse for pipeline IDs and status (failed/success/running)

3. Get Failed Pipeline Details

  • If failures: gitlab_ci_view(project="{{ project }}", pipeline_id="{{ first_failed_id }}")
  • gitlab_ci_trace(project="{{ project }}", pipeline_id="{{ first_failed_id }}")
  • Parse trace for error patterns: error:, failed:, exception, AssertionError, ModuleNotFoundError

4. Lint CI Config

  • gitlab_ci_lint(project="{{ project }}")

5. Optional: Trigger New Pipeline

  • If trigger_new: gitlab_ci_run(project="{{ project }}", branch="{{ branch }}")

6. Chain to CI Retry

  • If failures detected: suggest or run skill_run("ci_retry", '{"project": "{{ project }}"}')

7. Error Recovery

  • "no such host" → vpn_connect()
  • "unauthorized" → check GitLab token in config.json

8. Memory

  • memory_session_log("Checked CI health", "project={{ project }}, failures={{ has_failures }}")

Output

Report: recent pipelines (status per pipeline), CI config validation, failed pipeline analysis with errors and trace tail, debug commands (gitlab_ci_trace, gitlab_ci_run, gitlab_ci_cancel), and next step (ci_retry).

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