/suede-code · Code review + ship grade
Every merge gets a verdict it can't argue with.
Suede Code reviews current source, diffs, runtime behavior, and project rules, then returns evidence-based findings with an A-F ship grade. Use it when you explicitly ask an agent to review, grade, audit, security-check, or ship-gate a diff, PR, file, or release. It runs only when invoked.
View skill folder Install options
"grade this diff before I merge"
->
/suede-code
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-code review src/auth/login.ts
7 lanes armed · instant-F triggers live
P1 · session token written to logs · login.ts:88
SHIP GRADE: D · HOLD
fix brief attached · re-run to clear
Public install commands
Claude Code full-pack install:
/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-code .claude/skills/
Codex installer:
python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
--repo JasonColapietro/suede-creator-skills \
--path skills/suede-code
What it covers
- Deep, evidence-based code findings and a blunt A-F ship grade in one pass.
- File-level evidence, impact, and a concrete fix path for every blocking finding.
- Target, intent, and risk-lane mapping before judging a diff, PR, route, API, or release.
- Repo gates such as typecheck, lint, tests, dependency audit, and secret scanning when they exist.
- Instant-F triggers, language traps, OWASP checks, grade caps, and release-review modes.
- A deploy safety gate that turns the grade into ship, ship-with-caveats, or hold.
When to use it
- Use it for explicit review, grade, audit, security-check, or ship-gate requests.
- Use it on diffs, PRs, files, route changes, API changes, release builds, and fix verification.
- Use deeper review for auth, payments, migrations, public APIs, and cross-file behavior.
- Not for: findings-only review with Accessibility/SEO lanes (use suede-code-review).
- Not for: grade-only with no findings (use suede-code-grader).
- Not for: wiring CI or branch protection (use suede-ship-gate).
Best prompt
Use $suede-code to run a --standard review of the current diff against main. Intent: add checkout webhook handling. Risk lanes: backend, payments, data, auth, tests, and deploy readiness. Run available gates, report findings with file evidence, grade each lane, apply the deploy safety gate, and give the final ship gate.