suede-code-review

Reviews diffs and PRs with severity-ranked findings, deploy safety gates, and commit hygiene scans.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Code review often misses real breakage hidden outside the diff, produces noisy low-signal comments, or skips deploy-risk checks entirely. This Skill reviews a diff, PR, branch, or commit range with full context — changed files, callers, contracts, and deploy surface — and returns evidence-backed findings ranked P0–P3 plus a ship gate. ## Core Features & Use Cases - Severity-ranked findings: Every finding carries a file:line, evidence, a concrete fix path, and a confidence level, ordered P0 (data loss, security exposure) through P3 (cleanup). - Deploy Safety Gate and Commit Dirt Score: Automatically grades breaking changes, rollback safety, blast radius, env readiness, and scans the diff for secrets, debug artifacts, and conflict markers via a bundled shell script. - Stack-specific trap catalogs: Reference files cover TypeScript, React, Next.js, accessibility, SEO, database, Swift/iOS, OWASP 2025 baselines, and a twelve-smell maintainability baseline, loaded only when the diff touches that stack. - Use Case: Before merging a PR that touches auth and a database migration, run a --deep review to trace cross-file call chains, check OWASP baselines, and get a ship / ship-with-caveats / hold verdict with named blocking findings. ## Quick Start Ask the agent to use suede-code-review to review the current branch diff against main at standard depth and report findings with the deploy safety gate.

Frequently Asked Questions about suede-code-review

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

FAQPage Schema
How do I review a pull request for bugs before merging?

Point the skill at a branch, PR, or commit range and it pins the merge-base with a three-dot diff, runs the repo's own typecheck, lint, and test gates, then returns findings ranked P0–P3 with file:line evidence and fix paths. It ends with a ship, ship-with-caveats, or hold verdict.

What is the difference between quick, standard, and deep code review depth?

Quick is a pattern-based scan for obvious bugs and secrets in narrow diffs. Standard adds per-file correctness, language-specific traps, and test coverage on changed behavior. Deep traces the full import graph and call chains across files, recommended for auth, payment, migration, and public API changes.

Does this code review skill support Swift and iOS projects?

Yes, it ships a Swift and SwiftUI trap catalog covering force unwraps, retain cycles, main-thread violations, and Codable fragility. It also checks native contract drift, flagging API response or auth header changes that would break shipped iOS clients.

Can the review detect secrets or debug code left in a commit?

Yes, the Commit Dirt Score runs on every review via a bundled shell script that scans added diff lines for credentials, debug artifacts, conflict markers, staged build output, and oversized binaries. A dirty rating automatically sets the ship gate to hold.

When should I not use findings-only code review?

Use a different tool when you want an A-F letter grade, CI enforcement on every merge, or root-cause analysis of a live failing bug. This skill emits findings and a ship-gate recommendation only, and its gates are advisory rather than blocking.