andrewyazura

Critically challenge the current changes. Ask probing questions about edge cases, design decisions, and potential issues. Do not approve until all concerns are addressed.

Summarize uncommitted changes and suggest logical commit groupings with messages. Use before committing to plan clean, atomic commits.

Test-driven development workflow. Write failing tests first, then implement the minimum code to make them pass. Use when implementing features or fixing bugs.

Scan recently changed files for tech debt — dead code, duplication, bloated abstractions, and stale comments. Run at the end of a session to catch agent-introduced bloat.