Agent skill · practicalswan
resolving-merge-conflicts
Use when you need to resolve an in-progress git merge/rebase conflict.
What it needs
About 2k tokens when loaded.
What this skill does
1. See the current state of the merge/rebase. Check git history, and the conflicting files. 2. Find the primary sources for each conflict. Understand deeply why each change was made, and what the original intent was. Read the commit messages, check the PRs, check original issues/tickets. 3. Resolve each hunk. Preserve both intents where possible. Where incompatible, pick the one matching the merge's stated goal and note the trade-off. Do not invent new behaviour. Always resolve; never --abort. 4. Discover the project's automated checks and run them, typically typecheck, then tests, then format. Fix anything the merge broke. 5. Finish the merge/rebase. Stage everything and commit. If rebasing, continue the rebase process until all commits are rebased. <!-- MCP:START --> <!-- PORTABILITY:START --> Cross-Client Portability This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex. GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the workflow in project instructions when folder discovery is unavailable. Claude Code: keep the folder in a local skills directory or a compatible plugin source. Codex: install or sync the folder into $CODEXHOME/skills/resolving-merge-conflicts and restart Codex after major changes. <!-- PORTABILITY:END --> MCP Availability And Fallback Preferred MCP Server: None required Fallback prompt: "Use the Resolving Merge Conflicts skill without MCP. Rely on its local instructions, bundled resources, standard shell or editor tools, and direct verification. Show the evidence used before concluding." Do not claim an MCP operation was used when the active host does not expose it. Treat local files, tests, rendered outputs, logs, or screenshots as the fallback evidence path. <!-- MCP:END --> Anti-Patterns Activating resolving-merge-conflicts outside its documented task boundary. Skipping required source, prerequisite, safety, or approval checks. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills practicalswan/resolving-merge-conflicts