/suede-ship-gate · CI merge gate
CI that actually says no.
Suede Ship Gate wires CI and branch protection so one required check blocks bad merges without deadlocking path-filtered jobs. It detects apps, package managers, lockfiles, existing workflows, runtimes, deploy platform, and real scripts before writing workflows. It generates workflow files and exact protection settings, but it does not push, flip branch protection, or change repo access on its own.
View skill folder Install options
"make CI actually block bad merges"
->
/suede-ship-gate
Ask 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-ship-gate wire ci
stack detected: next.js + pnpm · lockfile pinned
one required check · no deadlock path
BRANCH PROTECTION: ON
bad merges bounce at the door
Public install commands
Claude Code full pack
/plugin marketplace add JasonColapietro/suede-creator-skills
/plugin install suede-skills@suede
Claude Code project-level copy
git clone https://github.com/JasonColapietro/suede-creator-skills.git /tmp/suede-creator-skills
mkdir -p .claude/skills
cp -R /tmp/suede-creator-skills/skills/suede-ship-gate .claude/skills/
Codex installer
python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
--repo JasonColapietro/suede-creator-skills \
--path skills/suede-ship-gate
What it covers
- 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-ship-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.