ci-images

Automates local CI parity checks and Docker image release readiness for publishing workflows.

1|1|Updated May 3, 2026
One-click install
npx skills add https://github.com/matt-riley/agent-skills --skill ci-images
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-images
Source: https://github.com/matt-riley/agent-skills/tree/main/skills/ci-images
Command: npx skills add https://github.com/matt-riley/agent-skills --skill ci-images

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Validate local CI parity and Docker image publishing readiness to streamline releases and reduce integration risk.

Core Features & Use Cases

  • Local CI parity validation: Compare local build artifacts, formatting, and tests against CI expectations.
  • Release readiness checks: Verify Docker image tagging conventions and publishing workflow before a release.
  • Preflight workflow guidance: Provide deterministic steps and artifacts to guide release engineers.

Quick Start

Run the release-readiness script to verify generated artifacts, formatting, and tests before publishing.

Frequently Asked Questions about ci-images

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

FAQPage Schema
How do I validate local CI parity before pushing Docker image releases?

Local CI parity validation compares local build artifacts, formatting, and tests against CI expectations. You can run a release-readiness script to verify generated artifacts and formatting before publishing Docker images.

What is Docker image release readiness checking?

Docker image release readiness checking verifies tagging conventions and publishing workflows before a release. It ensures generated artifacts, formatting, and tests pass preflight validation steps to reduce integration risk.

How do I automate preflight checks for Docker publishing workflows?

Automate preflight checks by running a release-readiness script that validates generated artifacts, formatting, and tests. This provides deterministic steps to guide release engineers and requires a clean working tree check before publishing.

Does CI parity validation require a clean working tree?

Yes, CI parity validation requires a clean working tree check before proceeding. The release-readiness script verifies that generation, formatting, and testing steps are complete and the working tree is clean.

Why does my local build pass but CI fail during Docker image publishing?

Local builds may pass while CI fails due to parity gaps in formatting, generated artifacts, or testing steps. Running local CI parity validation before release tagging identifies these integration risks early.

Can I verify Docker image tagging conventions locally before a release?

Yes, you can verify Docker image tagging conventions locally using release readiness checks. The validation script checks tagging conventions and publishing workflows to ensure pre-release validation passes across environments.