mobile-conflict-resolution-safe

Resolve Git merge conflicts in Android and Flutter repositories with safety checks.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Envy-7z/mobile-agent-skillpack --skill mobile-conflict-resolution-safe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile-conflict-resolution-safe
Source: https://github.com/Envy-7z/mobile-agent-skillpack/tree/main/skills/mobile-conflict-resolution-safe
Command: npx skills add https://github.com/Envy-7z/mobile-agent-skillpack --skill mobile-conflict-resolution-safe

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured and safe workflow for resolving Git merge conflicts in Android and Flutter projects, ensuring minimal behavior changes and explicit verification.

Core Features & Use Cases

  • Conflict Snapshotting: Identifies conflicted files and scans for conflict markers.
  • File-Type Specific Strategies: Applies tailored resolution approaches for UI, logic, and build files.
  • Enforced Safety Checks: Prevents architectural changes and hidden behavior modifications during conflict resolution.
  • Verification: Ensures tests pass and no conflict markers remain.
  • Reporting: Generates a clear report of decisions, resolutions, and risks.
  • Use Case: When merging a feature branch into your main development branch, you encounter merge conflicts. This Skill helps you resolve them systematically, ensuring the app's stability and intended behavior are preserved.

Quick Start

Use the mobile-conflict-resolution-safe skill to resolve the current git conflicts, prioritizing stable behavior and providing a verification report.

Frequently Asked Questions about mobile-conflict-resolution-safe

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

FAQPage Schema
How do I resolve Git merge conflicts in Android and Flutter repositories safely?

To resolve Git merge conflicts safely in Android and Flutter, you need a structured workflow that snapshots conflicts, applies file-type specific strategies, and enforces safety checks to prevent hidden behavior modifications.

What is the best way to handle merge conflicts in mobile UI and build files without breaking app behavior?

Handling merge conflicts in mobile UI and build files requires tailored resolution strategies for each file type, enforcing minimal edits and preserving tested paths to ensure the app's intended behavior and stability remain intact.

Can I prevent architectural changes while resolving Git conflicts in my mobile project?

You can prevent architectural changes during Git conflict resolution by using enforced safety checks that restrict modifications to minimal edits, ensuring tested paths are preserved and explicitly documenting all resolution decisions.

How do I verify that merge conflicts are fully resolved and tests pass in a Flutter or Android project?

To verify merge conflicts are fully resolved in Flutter or Android projects, run a verification step that ensures all tests pass and no conflict markers remain, followed by generating a report of resolutions and risks.

Why do I need to document decisions when resolving Git conflicts in mobile development?

Documenting decisions during Git conflict resolution in mobile development provides a clear verification report of what was changed, ensuring merge-safe outcomes and maintaining traceability of any risks introduced during the merge.

What should I do if my Git merge resolution introduces unintended behavior changes in my Android app?

If your Git merge resolution introduces unintended behavior changes in your Android app, you should enforce safety checks that prevent architectural modifications, prioritize minimal edits, and run verification to ensure tests pass.