/hyperpower:why

What a run decided, and what it assumed.

Reference

/hyperpower:why 4f2a --assumptions

When to use it

You are reviewing a diff you did not write, or explaining one to your team.

What you get

Each decision with its reason, and every assumption with its status.

How it works

The diff shows what changed. This command shows why.

--assumptions lists every assumption the run made. Each one has a status: verified, refuted, or unresolved.

Read the refuted ones first. Those assumptions turned out to be wrong, and the run shipped code anyway. If something in the diff looks odd, the reason is usually in that list.

--rejected shows the options the run considered and dropped, with a reason for each. Use it in review when someone asks why the run skipped the obvious approach. Often the run considered it and had a reason to drop it.

To fix a wrong assumption, use /hyperpower:correct.