Unslopify

Review tactical code quality through four complementary lenses:

• Contract strength: Do types, schemas, validation, and invariants express valid states?
• Single responsibility: Does each unit have a coherent reason to change?
• Failure integrity: Are failures handled deliberately rather than hidden?
• Knowledge duplication: Is the same rule encoded in multiple places?

Perform a review by default. Do not edit code unless the user explicitly asks for changes.

Select the scope

Honor an explicit user-provided review scope before applying defaults. Accept files, directories, snippets, diffs, commits, branches, pull-request refs, or the whole repository. A comparison-base option by itself configures branch comparison; it is not a review scope.

When the user does not specify a scope: