When several developers flag the same workflow problem—such as pull requests remaining open too long—combine their observations into one distinct weakness. Preserve the original comments as supporting detail rather than losing useful evidence. section 9.2.1
Use consolidation to make a code-review workflow easier to inspect and improve:
- Find duplicate edits or annotations, including repeated concerns about long-lived pull requests or direct production merges. section 9.2.1
- Combine each repeated concern into a single labeled weakness while retaining original comments as supplemental information. section 9.2.1
- Leave genuinely distinct weaknesses separate, then replace the corresponding workflow annotations with the consolidated weaknesses. section 9.2.1
- Walk through each weakness with the team, agree on an ideal state, and replace it with the approved solution. section 9.2.1
Figure 9.4 Consolidating duplicate comments into a single, identified weakness
Use the workflow diagram to compare repeated comments with the single identified weakness they represent. section 9.2.1
