One required check, and it cannot hang pending forever.
Path-filtered jobs are where required checks deadlock; this one aggregates them so a bad merge is blocked and a good one never waits on a job that did not run. The skill detects the stack, writes the workflow files, pins the runtime from the repo, and hands you the exact branch-protection settings to apply. It does not touch your repository access.
"make CI actually block bad merges"->/suede-ci-gateAsk in plain words. The router reads the request and loads this lane; MCP agents find it with list_suede_skills.
claude code · sample session
$ /suede-ci-gate wire cistack detected: next.js + pnpm · lockfile pinnedone required check · no deadlock pathBRANCH PROTECTION: ONbad merges bounce at the door
Inventory apps by manifest files, package-manager lockfiles, existing workflows, runtime files, deploy platform files, and real scripts before writing CI.
Create path-aware jobs per app behind a changes job, with an escape hatch so workflow-file edits run everything.
Add a ci-success aggregator that accepts successful or skipped app jobs and becomes the only required status check.
Match install commands to one lockfile per app and stop on dual-lockfile hygiene issues before wiring CI.
Pin Node, Python, and other runtimes from repo files instead of hardcoded guesses, and reconcile existing CI instead of duplicating it.
Return exact branch-protection settings plus a short report of apps detected, package managers, jobs, required checks, and fix-first issues.
When to use it
Adding CI after detecting the repo stack, package managers, lockfiles, workflows, runtime files, deploy platform, and real scripts.
Protecting main with one required ci-success check that holds when app jobs are skipped.
Fixing duplicate, hanging, skipped, or deadlocked required checks in GitHub Actions and branch protection.
Auditing whether a green gate actually executed jobs or only skipped everything.
Not for: reviewing or grading the code the pipeline runs on (use suede-code).
Not for: designing AI eval cases (use suede-ai-eval, then wire them in here).
Not for: Jason's private branch/worktree lifecycle, stale-mirror base selection, or finish/cleanup discipline (use suede-git-hygiene).
Best prompt
Use $suede-ci-gate to audit this repo's existing GitHub Actions, detect apps and lockfiles, add path-aware CI with a ci-success aggregator, and give me the exact branch protection settings for main.
It ships inside the Suede Creator Skills pack, so one install brings the whole pack and this skill with it. Claude Code takes two commands the first time and one after that; Codex installs the same pack natively.