How I review for this team
Set the posture once. Every repo inherits these unless it says otherwise.
local
organization defaults
Where a verdict landspostingDEFAULT · NOT YET TUNABLE
How — and whether — a review reaches GitHub.
What a reply can moveflipPostureLIVE
Replies are always verified against the code first. This is only what a verified reply may change.
How much I explainverbosityDEFAULT · NOT YET TUNABLETERSE → EXPOSITORY
An assumed-fluency spectrum — from naming what matters to teaching the system.
The bar for uncertain findingsconfidenceFloorDEFAULT · NOT YET TUNABLE
How high the bar sits before I post something I'm not fully sure of. Blocking concerns always post.
By concern typedimensions[]LIVEfocusdefaultnote-onlymuted
Any concern type not tuned here uses its standard stance. Muted ones I won't raise at all.
Nothing tuned yet — every concern type rests at its standard stance. Click a stance to steer my attention; tuned dimensions light up here.
WHAT THIS MEANS IN PRACTICE
On every PR, I post opinions without blocking, hold the gate until you re-request review, stay terse, and drop the low-confidence nits.