coding-triage

To resolve a stalled PR review, describe the current failure pattern to trigger recovery decision trees that diagnose root causes and select appropriate escalation and communication actions for your team.

The best way to triage CI failures is to apply structured recovery decision trees that diagnose the failure pattern and guide task decomposition and coordination to restore your CI pipeline.

Handle merge conflicts during team idle periods by following recovery guidance that diagnoses the stall and triggers task decomposition and coordination actions to re-engage the development workflow.

Yes, you can use this triage process for blocked PRs caused by unclear requirements, as it implements recovery decision trees covering six failure patterns including requirement ambiguity and team coordination.

No specific CI platforms or dependencies are required, as the triage workflow applies recovery strategies across software development projects generally without needing external integrations or setup scripts.

Avoid using coding triage workflows for routine PR review feedback that does not stall progress, as the decision trees specifically target failure patterns like review stalls, flaky CI, and team idle.