JasonColapietro/suede-creator-skills / skills/suede-code
suede-code
VerifiedUse when explicitly asked "review this PR" or to grade a diff, branch, or commit range. Suede returns evidence-backed P0-P3 findings, fix paths and an A-F ship grade; supports findings-only, grade-only and fix modes, seven review lanes, security checks, deploy safety and commit dirt. NOT FOR: automatic CI enforcement (use suede-ci-gate), agent evaluations (use suede-ai-eval), implementation-plan search (use suede-graph-flo-xr), or parallel fix coordination (use suede-agent-teams).
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.4 KB |
| SKILL.md | skill md | 18.8 KB |
| agents/openai.yaml | config | 433 B |
| references/grading-contract.md | markdown | 3.1 KB |
| references/maintainability-baseline.md | markdown | 3.4 KB |
| references/security-baselines.md | markdown | 3.3 KB |
| references/threat-verify.md | markdown | 1.4 KB |
| references/traps-swift-ios.md | markdown | 3.7 KB |
| references/traps-web.md | markdown | 10.7 KB |
| references/usage-contract.md | markdown | 842 B |
| references/worked-example-grade-only.md | markdown | 7.9 KB |
| references/worked-example.md | markdown | 11.3 KB |
| scripts/commit-dirt-scan.shexecutable | script | 3.3 KB |
references/threat-verify.md
View on GitHub# --threat-verify Mode
Verify that threat mitigations declared in a threat model (ADR threat table, PLAN.md risk section, or an architecture review's threat table) are actually implemented in the codebase.
**Trigger:** pass `--threat-verify` or say "verify threat mitigations" / "check threat model compliance"
**Input:** threat model source: file path or pasted content. Accepted formats: ADR threat table, PLAN.md risk section, free-form "Threat: X / Mitigation: Y" pairs.
**Process:**
1. Parse the threat model into: { threat_id, description, declared_mitigation, expected_location }
2. For each threat: grep the codebase for the declared mitigation at ALL relevant entry points (routes, handlers, middleware, auth layers)
3. Classify each threat:
- **CLOSED**: mitigation confirmed at all relevant entry points
- **OPEN**: mitigation partially implemented (found in some but not all entry points)
- **UNREGISTERED**: no evidence of declared mitigation in codebase
4. Output THREAT-REVIEW.md:
```
| Threat ID | Description | Declared Mitigation | Status | Evidence | Gaps |
| --- | --- | --- | --- | --- | --- |
```
**Blockers:** OPEN and UNREGISTERED items are reported as blockers: the recommendation is to close them before shipping; the user makes the final call.
**What this is NOT:** This mode does not scan for new vulnerabilities (that is what the OWASP lane does). It only verifies previously declared mitigations exist.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |