fix(bugfix): always recommend /review before /pr in controller

In testing, the agent skipped /review and recommended /pr directly
after /test, rationalizing that the fix was simple. Add targeted
guidance: always recommend /review before /pr — the agent implemented
the fix and is not in a position to objectively evaluate its quality.
Only the user can decide to skip review.

Made-with: Cursor

Author: jwm4

workflows/bugfix/.claude/skills/controller/SKILL.md

@@ -91,6 +91,12 @@ After presenting results, consider what just happened, then offer options that m
 - A trivial fix might go straight from `/fix` → `/test` → `/review` → `/pr`
 - If the user already has their own PR process, they may stop after `/review`
 
+**Always recommend `/review` before `/pr`.** Do not recommend skipping review, even for
+fixes that seem simple or mechanical. You implemented the fix and wrote the
+tests — you are not in a position to objectively evaluate their quality.
+Review exists precisely to catch what the fixer misses. Only the user can
+decide to skip it.
+
 ### How to Present Options
 
 Lead with your top recommendation, then list alternatives briefly: