Evidence-Driven Code Simplification

Reduce demonstrated implementation cost while preserving the behavior and constraints the repository actually depends on. Never infer how code was authored or use "slop" as a finding; describe the concrete problem instead.

Preserve scope and authority

• Read applicable repository instructions and record the initial Git state. Preserve unrelated staged, unstaged, and untracked work.
• Treat a review request as read-only. Edit only when the user requests simplification or refactoring, and only within the authorized scope.
• Do not install or introduce analyzers, packages, runtimes, workloads, or tools. Route any proposed addition through $audit-dependencies when that skill is available.
• Do not weaken tests, broaden suppressions, swallow failures, replace errors with success-like defaults, or perform mass cleanup to make the result look simpler.
• Use repository-native, already-installed tests, builds, type checks, and linters. Do not run rewriting tools unless the user authorized their exact output scope.
• Keep private source and diagnostics local by default. Redact secrets and sensitive values from reports.

Select one mode

• Focused review: inspect the requested C# or Python scope and report verified simplification opportunities without editing.
• Refactor: make the smallest coherent behavior-preserving change requested by the user.
• Enforcement: run, or adjust the configuration of, an already-configured repository tool only when the user explicitly requests enforcement work. Missing tooling is a gap, not permission to install it.