github-actions-efficiency

Audit GitHub Actions workflows and recommend fixes to reduce CI minutes and costs.

3|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill github-actions-efficiency-jose-polanco-oxte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-actions-efficiency
Source: https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer/tree/main/.agents/skills/ci-cd/sub-skills/github-actions-efficiency
Command: npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill github-actions-efficiency-jose-polanco-oxte

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? GitHub Actions workflows often waste CI minutes through missing dependency caches, absent concurrency cancellation, over-broad triggers, and bloated test matrices, driving up costs and slowing feedback loops. ## Core Features & Use Cases - Workflow Auditing: Measures existing workflows with ripgrep and the gh CLI to find missing caches, missing concurrency cancellation, duplicate coverage, and over-broad triggers. - Guardrailed Fix Selection: Applies five safety rules so recommended fixes never hide required release, migration, or shared-library validation, then ranks the top 3 fixes by estimated daily CI minutes saved. - Live Validation: Verifies path-gating and stale-run cancellation with real test pushes when gh CLI access is available, and clearly labels static-only analysis when it is not. - Use Case: A team notices their CI bill climbing. The skill inspects .github/workflows/, finds every push runs a full 12-leg matrix with no caching, and recommends lockfile-keyed caching, concurrency cancellation, and a reduced matrix for ordinary code changes. ## Quick Start Audit the GitHub Actions workflows in this repository and recommend the top fixes to reduce CI minutes and cost.

Frequently Asked Questions about github-actions-efficiency

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

FAQPage Schema
How do I reduce GitHub Actions CI costs and runtime?

Start by measuring existing workflows for missing dependency caches, missing concurrency cancellation, over-broad triggers, and duplicate coverage. Then apply the highest-impact fixes first, such as lockfile-keyed caching and cancel-in-progress concurrency groups, ranked by estimated daily CI minutes saved.

How to add dependency caching to a GitHub Actions workflow?

Use actions/cache@v4 with a key based on your lockfile, such as hashFiles('**/package-lock.json'), and a restore-keys fallback prefix. Adapt the cache path to your ecosystem, for example ~/.npm for Node.js projects.

Can I audit GitHub Actions workflows without gh CLI access?

Yes, paste the .github/workflows/ contents and recent run output for a static-only analysis. The audit will note that findings are based on provided files only and not confirmed with live runs.

When should I reduce the GitHub Actions test matrix?

Match matrix breadth to the decision being made: full matrix for releases, a reduced compatibility matrix for runtime or packaging changes, and a single representative leg for ordinary code changes. Never drop legs that have an explicit version or platform commitment.

Why is concurrency cancellation important in GitHub Actions?

Without a concurrency group with cancel-in-progress: true, every new push leaves stale runs consuming runner minutes. Adding cancellation stops outdated runs immediately, cutting wasted spend on superseded commits.