mobile-pr-merge-gatekeeper

Analyze Android and Flutter pull request diffs and classify findings by severity.

Updated Mar 5, 2026

Search Tags:#code quality #pr review #mobile development #android #flutter #merge gate

Ready to run

npx skills add https://github.com/Envy-7z/mobile-agent-skillpack --skill mobile-pr-merge-gatekeeper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mobile-pr-merge-gatekeeper
Source: https://github.com/Envy-7z/mobile-agent-skillpack/tree/main/skills/mobile-pr-merge-gatekeeper
Command: npx skills add https://github.com/Envy-7z/mobile-agent-skillpack --skill mobile-pr-merge-gatekeeper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enforces a strict, evidence-based review process for mobile pull requests, preventing risky merges and ensuring code stability for Android and Flutter projects.

Core Features & Use Cases

Automated Risk Assessment: Analyzes code changes for architectural violations, concurrency issues, UI regressions, and test coverage.
Severity Classification: Assigns findings to P0 (blocker), P1 (high), P2 (medium), or P3 (low) severity levels.
Merge Decision: Provides a clear BLOCK, APPROVE WITH NOTES, or APPROVE decision based on findings.
Merge Notes Generation: Produces concise notes detailing required fixes, verification steps, and risk summaries.
Use Case: A junior developer submits a PR for a new feature. The gatekeeper skill reviews the changes, identifies a potential null pointer exception (P1), and blocks the merge until it's fixed, providing clear instructions on how to resolve it.

Quick Start

Use the mobile-pr-merge-gatekeeper skill to review the current pull request and provide a merge decision.

Frequently Asked Questions about mobile-pr-merge-gatekeeper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate PR review and block risky merges for Android and Flutter codebases?▼

Automated PR review for Android and Flutter codebases analyzes diffs to classify findings by severity (P0-P3) and blocks risky merges. It assesses architectural violations, concurrency issues, UI regressions, and test coverage to ensure code stability.

How does severity classification work during a mobile pull request risk assessment?▼

Severity classification assigns findings to P0 (blocker), P1 (high), P2 (medium), or P3 (low) levels based on code change analysis. This system evaluates architectural violations, concurrency issues, UI regressions, and test coverage to determine a final merge decision.

Can I use this merge gate to review UI regressions and concurrency issues?▼

Yes, the merge gate enforces an evidence-based review process that specifically analyzes code changes for UI regressions and concurrency issues. It uses these findings to generate a BLOCK, APPROVE WITH NOTES, or APPROVE decision with actionable merge notes.

What's the best way to prevent junior developers from merging risky mobile code changes?▼

The best way to prevent risky merges is an evidence-based gatekeeper that blocks pull requests until critical issues are fixed. It identifies high-severity problems like null pointer exceptions and provides clear instructions on how to resolve them before approval.

Do I need to run a snapshot script before reviewing mobile pull request diffs?▼

Yes, you must execute a snapshot script to gather diff context and risk assessment before the review process. This script provides the necessary evidence-based context for the skill to analyze architectural changes and classify findings accurately.

Why does my mobile PR merge get blocked even when tests pass?▼

A mobile PR merge gets blocked when the review workflow identifies high-severity findings like architectural violations or concurrency issues beyond test coverage. The gatekeeper prioritizes code stability by blocking merges until these P0 or P1 risks are resolved.