What problem does it solve? Merging feature branches back into develop without systematic checks leads to broken builds, unresolved conflicts, unsynced documentation, and failed CI runs. This Skill enforces a complete pre-merge quality gate so every branch passes build, test, lint, and documentation checks before merging. ## Core Features & Use Cases - Pre-Merge Self-Check: Runs a checklist covering uncommitted files, test execution, doc synchronization, develop sync status, public file isolation, and cross-module declarations, outputting a PreMergeChecklist JSON where all_pass=false blocks the merge. - Conflict Prediction: Uses git merge-tree to detect merge conflicts before merging, classifying severity (high/medium/low) with explicit merge policies per level. - SwiftLint Strict & Doc Sync: Enforces swiftlint lint --strict on Swift changes and maps code modifications to the documentation that must be updated. - Use Case: Before merging a feature branch into develop, run the pre-merge check script to get a JSON report; if SwiftLint fails or conflicts exceed 5 files, the merge is blocked until resolved. ## Quick Start Ask the AI to run the pre-merge check on my current feature branch and tell me whether it is safe to merge into develop.