no-sus-code-doctor

Run a strict Dedalus STYLE-informed code-quality doctor for agent-authored PRs. Use when Kevin says "no sus code", "strict review", "quality doctor", "get this to 100", "prove this works", "review try/catches/fallbacks/ensure patterns", "review retries/timeouts/hooks/lint ignores", or before shipping high-risk auth, billing, Stripe, fraud, onboarding, credit, admin, infra, or security changes.

Category
Engineering
Skill
106 of 261
Source
Kevin wiki

This skill is a scored shipping gate for code that must survive skeptical Dedalus review. It assumes the diff is wrong until the implementation proves the invariant, the interface, the error model, and the user-visible behavior.

The goal is not "passes lint." The goal is "a reviewer cannot find hidden fallback behavior, unclear ownership, loose types, vague errors, async/sync mismatch, fake proof, frontend shortcuts, or PR hygiene problems."

Use this before asking a human or second model to review high-risk code. It complements gstack-review and autoreview: this skill is the deterministic self-audit and fix loop that brings the diff to a real 100.

Progressive Disclosure

This SKILL.md is the routing layer. Detailed recipes, examples, integration notes, and troubleshooting guidance live in references/details.md so they are loaded only when the task needs them.

Before producing concrete output, making a design recommendation, or debugging an implementation, load the relevant reference section below. Do not rely on memory for branch-specific APIs, examples, or caveats.

Task branchRead first
Source Orderreferences/details.md#source-order
Scorereferences/details.md#score
Audit Loopreferences/details.md#audit-loop
Smell Scansreferences/details.md#smell-scans
Audit Matrixreferences/details.md#audit-matrix
Function and Interface Rulesreferences/details.md#function-and-interface-rules
Comment and Preamble Rulesreferences/details.md#comment-and-preamble-rules
Error Rulesreferences/details.md#error-rules
Verification Requirementsreferences/details.md#verification-requirements
Outputreferences/details.md#output
No-Sus Code Doctorreferences/details.md#no-sus-code-doctor
  • gstack-review - staff-level code review after this self-audit.
  • autoreview - structured pre-merge closeout once the local score is clean.
  • vibe-code-doctor - broader project health for inherited/AI-generated apps.
  • tests - invariant-first test design and smallest honest verification.
  • fail-closed-case-matching - product logic that must reject ambiguous states.
  • rtfm - verify external API behavior before coding against it.
  • codebase-design - deep modules, small interfaces, and deletion tests.
  • generate-interface - define the public surface before implementation.
  • comment - docstrings and comments that earn their keep.