suede-ci-gate

Generates path-aware GitHub Actions CI workflows and branch-protection settings for any repository.

123|10|Updated May 24, 2026
One-click install
npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-ci-gate-jasoncolapietro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: suede-ci-gate
Source: https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-ci-gate
Command: npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-ci-gate-jasoncolapietro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams set up CI that looks green but gates nothing: required checks that hang pending forever because path-filtered jobs skip, duplicate workflows that conflict, and hardcoded runtime versions that drift from production. This skill wires a pipeline that actually blocks a bad merge. ## Core Features & Use Cases - Stack detection first: inventories apps, package managers, lockfiles, runtime versions, existing workflows, and deploy platforms before writing any YAML. - Deadlock-proof aggregator gate: emits a single ci-success required check that treats skipped path-filtered jobs as passing, so unrelated PRs never hang. - Lockfile and runtime hygiene: enforces one lockfile per app with the matching install command, and pins Node/Python versions from .nvmrc, engines, or .python-version. - Use Case: Point it at a Next.js repo with no CI and Vercel previews disabled; it produces a path-filtered workflow with lint, typecheck, test, and build jobs, plus the exact gh api branch-protection commands requiring only ci-success. ## Quick Start Ask the agent to use suede-ci-gate to set up path-aware CI and branch protection for this repository, detecting the stack first.

Frequently Asked Questions about suede-ci-gate

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

FAQPage Schema
How do I set up branch protection with path-filtered GitHub Actions jobs?

Never require path-filtered jobs directly, since a skipped job leaves the PR pending forever. Add one aggregator job with `if: always()` that needs all app jobs and accepts success or skipped results, then require only that aggregator in branch protection.

Why is my required status check pending forever on a pull request?

The required check is a path-filtered job that skipped because the PR touched no matching paths, so it never reports a result. Replace it with an aggregator job that always runs and treats skipped dependencies as passing.

Does this CI setup work with pnpm, yarn, or bun monorepos?

Yes. The skill detects the lockfile per app (package-lock.json, pnpm-lock.yaml, yarn.lock, bun.lockb) and emits the matching install command such as `pnpm i --frozen-lockfile`. Two lockfiles in one app are flagged to fix before wiring CI.

Can the skill apply branch protection settings automatically?

No. It writes workflow files and outputs the exact protection settings and `gh api` commands, but the user applies them. Afterward it verifies with `gh api` that required checks contain only the aggregator, or reports the gate as unverified.

When should CI include a build job if my deploy platform already builds?

Include a build job when the platform skips non-production builds, such as a Vercel `ignoreCommand` that disables previews. In that case CI is the only pre-merge proof the app compiles, so the build job is mandatory.