skills.rest
KingInYellows
KingInYellowsOFFICIAL
Explore all skills by this author →
GitHub

ci-conventions

Standardize CI failure analysis for self-hosted GitHub Actions runners.

Updated Jan 10, 2026
Search Tags:#security#validation#patterns#github-actions#ci#self-hosted
One-click install
npx skills add https://github.com/KingInYellows/yellow-plugins --skill ci-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-conventions
Source: https://github.com/KingInYellows/yellow-plugins/tree/main/plugins/yellow-ci/skills/ci-conventions
Command: npx skills add https://github.com/KingInYellows/yellow-plugins --skill ci-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Centralizes CI analysis conventions, including validation rules, failure catalogs, error catalogs, and security patterns for self-hosted GitHub Actions runners and automation agents.

Core Features & Use Cases

  • Validation Schemas: runner names, IDs, SSH hosts and input validation guidelines.
  • Failure Pattern Library: catalog of common CI failure signals (F01-F12) with suggested fixes and quick grep patterns.
  • Security Rules & Redaction: guidance on secret redaction, log sanitization, and secure runner configuration.

Quick Start

Load the reference catalogs (references/failure-patterns.md, references/security-patterns.md) and begin diagnosing a failing run with the provided patterns.

Frequently Asked Questions about ci-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose GitHub Actions CI failures on self-hosted runners?▼

Diagnose GitHub Actions CI failures by loading centralized reference catalogs containing validation schemas, failure patterns (F01-F12), and suggested fixes to standardize analysis for self-hosted runners.

What are common self-hosted GitHub Actions failure patterns?▼

Common self-hosted GitHub Actions failure patterns are cataloged as signals F01 through F12, providing quick grep patterns and suggested fixes to identify and resolve recurring workflow configuration errors.

How do I validate runner names and SSH hosts for GitHub Actions workflows?▼

Validate runner names, IDs, and SSH hosts for GitHub Actions workflows by applying centralized validation schemas and input validation guidelines to ensure correct runner configuration.

How do I redact secrets and sanitize logs in self-hosted CI runners?▼

Redact secrets and sanitize logs in self-hosted CI runners by applying security rules and redaction guidance from the security-patterns reference catalog to secure your workflow configuration.

Does this CI failure analysis tool work with standard GitHub Actions workflows?▼

Yes, this CI failure analysis tool works with standard GitHub Actions workflows by providing linter rules and validation schemas to audit and validate workflow configurations specifically on self-hosted runners.

Related Skills

Explore More Software Engineering Skills→
rodrigotoledorodrigotoledo

gh-fix-ci

Identify failing GitHub PR checks and extract failure snippets from Actions logs.

Community
Advanced
LongTermSupportLongTermSupport

phpstan-runner

Executes PHPStan static analysis and iteratively applies fixes until clean.

Official
Intermediate
amdmaxamdmax
2

github-runner-setup

Automate setup, security hardening, and monitoring of macOS GitHub Actions self-hosted runners.

Community
Advanced
KingInYellowsKingInYellows

diagnose-ci

Diagnose GitHub Actions CI failures on self-hosted runners using failure patterns F01-F12.

Official
Intermediate