github-workflows

What problem does it solve?

This Skill optimizes GitHub Actions for monorepos, preventing unnecessary CI/CD runs and reducing feedback loop times. It solves the problem of wasted compute resources and slow development cycles caused by unrelated changes triggering full pipelines, ensuring only relevant jobs execute.

Core Features & Use Cases

• Path-Scoped Triggers: Uses paths-filter to ensure jobs only run when relevant files (e.g., rust/**, js/**) are changed, drastically reducing CI/CD execution time.
• Optimized Language-Specific Jobs: Provides battle-tested patterns for Rust, Python (uv), and TypeScript jobs, including caching, performance tools (sccache, mold), and specific linters/testers.
• Guarded Vercel Previews: Automatically builds Vercel previews only when frontend paths change, saving deployment costs and ensuring relevant previews are generated.
• Use Case: In a monorepo with a Rust backend and a TypeScript frontend, a change to only the Rust code will trigger only the Rust CI jobs, skipping all TypeScript and Vercel preview jobs, saving time and resources.

Quick Start

To set up a GitHub Actions workflow that only runs Rust tests when files in the 'rust/' directory change, configure your workflow's 'on' trigger with a 'paths' filter for 'rust/**'.