Repository navigation
docs(claude): spell out issue priority order and tie-breakers - #75
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Warning Review limit reached
This review includes 1 billable file and costs up to $0.25.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Or wait 56 minutes for your next included review. View limit details
Comment |
|
Merge-driver verdict: CLEAN at An independent adversarial reviewer (Sonnet, high effort, cold brief, not the author) reviewed the full diff. It found no blocking findings. Local verification (real, docs-only change):
Non-blocking notes:
Gate items:
|
Spells out the full issue pick order in the "Issue assignment" section, step 1: priority/p0 to p3 then unlabelled; within a level urgency, then impact, then unblocks-others, then smaller effort; ties oldest first; skip blocked, needs-info, wontdo, and anything assigned, claimed or with an open PR. Previously it only said "oldest first within a priority". The same wording is applied in all four cloud-commitments repos (go and cli follow once #421 and #2202 merge).
Docs only. No closing issue, so label mirroring does not apply.
🤖 Generated with Claude Code