yellow-ci

Plugin yellow-ci from marketplace yellow-plugins in KingInYellows/yellow-plugins. Commands read from the repo's manifest — today.

Skills (8)

• ci-conventions

  Shared CI conventions reference (not an executable action) — validation rules, failure patterns (F01-F12), error catalog, and security patterns. Consult when agents or commands need CI-specific validation or pattern-matching reference.

• ci-diagnose

  Diagnose a CI failure now — fetch the failed run, redact and match its logs against the F01-F12 pattern library, and report root cause with fixes. Use when a GitHub Actions run has failed and you want its root cause and a fix now (for the reference workflow guide, use the diagnose-ci skill).

• ci-lint-workflows

  Lint GitHub Actions workflows for self-hosted runner issues (W01-W14). Use when checking workflows before pushing or finding common CI pitfalls; previews and confirms before applying any fix.

• ci-runner-health

  Check self-hosted runner health via SSH, with deep runner diagnostics folded in. Use when the user asks for runner status, whether a runner is healthy, or wants to verify infrastructure before diagnosing CI failures.

• ci-setup-runner-targets

  Configure runner pool targets, routing rules, and semantic metadata for CI workflow optimization (wizard, YAML import, or GitHub API discovery). Use when setting up runner-aware CI optimization or after changing your runner fleet.

• ci-setup

  Check CI prerequisites and configure the self-hosted runner SSH config. Use when first installing the plugin, after adding runners, or when CI commands fail with auth or connectivity errors.

• ci-status

  Show recent CI workflow run status. Use when the user asks for CI status, recent builds, what is running, or needs to find a run ID for diagnosis.

• diagnose-ci

  Reference guide (not an executable action) for CI debugging workflows and the F01-F12 failure-pattern catalog on self-hosted runners. Consult when you need to understand debugging workflows or failure patterns; to actually run a diagnosis, use the ci-diagnose skill instead.

Slash commands (9)

• /yellow-ci:ci:diagnose

  Diagnose CI failure and suggest fixes. Use when user wants to analyze a failed GitHub Actions run, understand why CI broke, or get actionable fix suggestions.

• /yellow-ci:ci:lint-workflows

  Lint GitHub Actions workflows for self-hosted runner issues. Use when user wants to check workflows before pushing, asks \"lint CI\", \"check workflows\", or wants to find common pitfalls in their GitHub Actions configuration.

• /yellow-ci:ci:report-linear

  Diagnose a CI failure and create a Linear bug issue. Use when CI has failed and you want to track the fix in Linear. Requires yellow-linear to be installed.

• /yellow-ci:ci:runner-cleanup

  Clean Docker images/containers, old logs, and caches on self-hosted runner. Destructive operation with dry-run preview and confirmation. Use when runner disk is full, Docker space needs freeing, or old CI logs need pruning.

• /yellow-ci:ci:runner-health

  Check self-hosted runner health via SSH. Use when user asks \"runner status\", \"is runner healthy\", \"check runner\", or wants to verify infrastructure before diagnosing CI failures.

• /yellow-ci:ci:setup-runner-targets

  Configure runner pool targets, routing rules, and semantic metadata for CI workflow optimization. Supports interactive wizard, YAML import, and GitHub API discovery. Use when setting up runner-aware CI optimization or after changing your runner fleet.

• /yellow-ci:ci:setup-self-hosted

  Inventory available self-hosted runners and optimize workflow jobs to use the best runner based on labels, OS, and live load. Use when runner assignments look suboptimal, jobs are queuing on the wrong runner, or after registering new self-hosted runners.

• /yellow-ci:ci:setup

  Check CI prerequisites and configure self-hosted runner SSH config. Use when first installing the plugin, after adding runners, or when ci commands fail with auth or connectivity errors.

• /yellow-ci:ci:status

  Show recent CI workflow run status. Use when user asks \"CI status\", \"recent builds\", \"what's running\", or needs to find run IDs for diagnosis.

Hooks (1)

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/entrypoint-claude.js"

Similar plugins