Mobile PR Merge Gatekeeper

Overview

Run a strict, evidence-based PR review workflow that protects stability and prevents risky merges.

Workflow

1. Collect diff context

• Run scripts/mobile_pr_gate_snapshot.sh <repo_root> first.
• Identify changed modules, risky file types, test impact, and release-sensitive areas.

2. Review by risk class

• Architecture boundary violations.
• Coroutine/async safety and state handling.
• UI regressions (Compose/XML/Flutter).
• API/DTO mapping safety and nullability.
• Tests and verification coverage.

3. Classify findings

• P0: must block merge.
• P1: high risk, block unless fixed.
• P2: non-blocking but should be fixed soon.
• P3: improvement/nit.

4. Decide merge gate

• BLOCK: any unresolved P0/P1.
• APPROVE WITH NOTES: only P2/P3 remain.
• APPROVE: no meaningful findings.

5. Produce merge notes

• Include required fixes, optional follow-ups, and verification commands.
• Keep patch recommendations minimal and scoped.

Output Format

Use this structure:

# PR Merge Gate Report

## Decision
BLOCK | APPROVE WITH NOTES | APPROVE

## Critical Findings (P0/P1)
1. ...

## Non-Critical Findings (P2/P3)
1. ...

## Required Before Merge
1. ...

## Verification
- Commands run / required:
- Evidence summary:

## Merge Notes
- Risk summary:
- Follow-up tasks:

Guardrails

• No merge recommendation without evidence.
• No architecture rewrites during review feedback.
• No speculative fixes; anchor comments to concrete risks.
• If confidence is low, default to BLOCK with precise next checks.

Resources

• scripts/mobile_pr_gate_snapshot.sh
• references/review-severity-rubric.md
• references/merge-gate-checklist.md