personal-environment

Assess what is possible in a software project and provide evidence-backed answers. Use when users ask what can be done, how specific business rules behave, how code will react to a payload, or when behavior is uncertain and must be validated by call-chain backtracking or automated tests instead of code reading alone.

Review pull requests using only `git diff origin/main` or `origin/master` as the diff command. Use to critique changes for clean code issues (overengineering, SRP/DRY/KISS violations, nested conditionals, null-safety misuse, poor naming), plus framework/language misconceptions by cross-checking repository docs (README, conventions) and the surrounding code context. Use when a user asks to review a PR and may provide an intended goal via a `#blabla` placeholder to replace.