actions-ci-tuning

Analyze and tune DevOps workflows and artifact handling for better performance and reliability.

320|3|Updated Apr 24, 2026

Search Tags:#cache #playwright #github-actions #ci-cd #parallelism #test-sharding

Ready to run

npx skills add https://github.com/mizchi/skills --skill actions-ci-tuning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: actions-ci-tuning
Source: https://github.com/mizchi/skills/tree/main/devops/actions-ci-tuning
Command: npx skills add https://github.com/mizchi/skills --skill actions-ci-tuning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and tune GitHub Actions workflows to improve reliability and speed.

Core Features & Use Cases

Cache optimization: configure and verify npm/pnpm/yarn caches to reduce CI run times.
Parallelism & test sharding: split jobs and tests to maximize throughput without compromising correctness.
Artifact guards & reliability: implement guards and reporting to avoid flaky merges and missing artifacts.
Playwright patterns: apply Playwright-specific patterns to stabilize end-to-end tests.

Quick Start

Audit existing workflows, identify cache misses and flaky shard issues, and implement a minimal tuning plan.

Frequently Asked Questions about actions-ci-tuning

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

FAQPage Schema

How do I fix slow GitHub Actions CI runs with cache misses and flaky shard tests?▼

To fix slow GitHub Actions CI runs, audit existing workflows to identify cache misses and flaky shard tests, then apply a tuning plan covering cache setup, job parallelism, test sharding, and artifact guards to improve reliability and speed.

What is the best way to configure npm or pnpm caches in GitHub Actions?▼

The best way to configure npm or pnpm caches in GitHub Actions is to verify and apply explicit caching strategies within your workflow setup to reduce CI run times and prevent cache misses.

How do I split Playwright end-to-end tests across parallel jobs in GitHub Actions?▼

To split Playwright end-to-end tests across parallel jobs, apply Playwright-specific patterns with shard-based test splitting to maximize throughput and stabilize end-to-end test execution without compromising correctness.

Why does my GitHub Actions workflow fail on merge with missing artifacts and flaky tests?▼

GitHub Actions workflows fail on merge with missing artifacts when artifact guards and reporting are not implemented. Apply a checklist-driven workflow with artifact handling guards to avoid flaky merges and missing test outputs.

Can I use test sharding to maximize job parallelism without compromising correctness in GitHub Actions?▼

Yes, you can use test sharding to maximize job parallelism in GitHub Actions. Split jobs and tests systematically to increase throughput while maintaining correctness through explicit parallelism planning and artifact guards.