git-merge-conflict-resolution
Git Merge Conflict Resolution
Overview
Use this skill to resolve conflicts without silently dropping behavior from either side.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Semantic conflict triage:
references/semantic-conflict-triage.md
Templates And Assets
- Resolution log template:
assets/conflict-resolution-log-template.md
- Verification checklist:
assets/conflict-verification-checklist.md
Inputs To Gather
- Conflicted files and conflict types.
- Intent of each conflicting change set.
- Required tests and high-risk behavioral paths.
- Domain-owner contacts for ambiguous semantic conflicts.
Deliverables
- Conflict resolution decisions with rationale.
- File-level intent mapping for resolved hunks.
- Verification evidence for resolved behavior.
Workflow
- Classify conflicts by behavioral impact and risk.
- Resolve textual conflicts while preserving intent from both sides.
- Log rationale in
assets/conflict-resolution-log-template.md. - Validate with
assets/conflict-verification-checklist.md. - Escalate unresolved semantic ambiguity using
references/semantic-conflict-triage.md.
Quality Standard
- Every resolved hunk has explicit intent rationale.
- No conflict markers remain.
- Affected behaviors are re-verified by tests/manual checks.
- High-risk semantic merges receive domain-owner review.
Failure Conditions
- Stop when change intent cannot be reconstructed confidently.
- Stop when semantic correctness cannot be verified post-resolution.
- Escalate when domain arbitration is needed for ambiguous merges.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9