ci-hygiene

Inspect GitHub Actions workflows and Dockerfiles for CI/CD best practices.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/youssefKadaouiAbbassi/yka-code --skill ci-hygiene-youssefkadaouiabbassi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-hygiene
Source: https://github.com/youssefKadaouiAbbassi/yka-code/tree/main/skills/ci-hygiene
Command: npx skills add https://github.com/youssefKadaouiAbbassi/yka-code --skill ci-hygiene-youssefkadaouiabbassi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enforces best practices for CI/CD configurations to make them deterministic, secure, and reproducible, by checking and suggesting improvements in GitHub Actions workflows, Dockerfiles, and other CI-related configurations.

Core Features & Use Cases

  • CI/CD Configuration Checks: Inspects CI configurations for common issues like outdated versions, unsecured secrets, and lack of reproducibility.
  • Claude Code Usage Guidelines: Ensures proper use of Claude Code in CI to maintain performance and security.
  • Version Pinning: Enforces pinning of versions for GitHub Actions, Docker images, and dependencies to avoid breakages.
  • Use Case: For developers working on a CI/CD pipeline for their application, this Skill helps maintain high standards and reduces the likelihood of CI failures.

Quick Start

Activate the ci-hygiene skill when you are editing your GitHub Actions workflow or Dockerfile.

Frequently Asked Questions about ci-hygiene

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

FAQPage Schema
How do I enforce version pinning in GitHub Actions workflows and Dockerfiles?

Enforce version pinning in GitHub Actions and Dockerfiles by using this Skill to inspect CI configurations, identify floating tags or unsecured dependencies, and suggest pinned versions for improved reproducibility and security.

What is CI hygiene and why do I need it for my CI/CD pipeline?

CI hygiene is the practice of making CI/CD configurations deterministic, secure, and reproducible. You need it to reduce the likelihood of CI failures by enforcing best practices for version management and secret handling across workflows.

How do I check my Docker Compose configurations for unsecured secrets?

Check Docker Compose configurations for unsecured secrets by applying this Skill to inspect your CI-related files, detect improper secret management, and receive actionable suggestions to secure your pipeline.

Can I use this to ensure proper usage of Claude Code in CI?

Yes, you can use this Skill to ensure proper usage of Claude Code in CI environments by enforcing specific guidelines that maintain performance and security standards within your automated workflows.

Does this Skill work without requiring external dependencies?

Yes, this Skill works without requiring external dependencies, operating directly on your existing CI/CD configurations like GitHub Actions workflows and Dockerfiles to evaluate and enforce reproducibility rules.

What's the best way to prevent breakages from outdated GitHub Actions versions?

Prevent breakages from outdated GitHub Actions versions by using this Skill to inspect your workflows for outdated dependencies and enforce strict version pinning, ensuring stable and reproducible pipeline executions.