Resolving merge conflicts
Use when you need to resolve an in-progress git merge/rebase conflict.From its SKILL.md
npx -y skills add adriannoes/awesome-agentic-ai --skill resolving-merge-conflictsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
0.9 KB, 178 tokens by cl100k_base, as published. Nobody here has run it
-
See the current state of the merge/rebase. Check git history, and the conflicting files.
-
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.
-
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. -
Discover the project's automated checks and run them — typically typecheck, then tests, then format. Fix anything the merge broke.
-
Finish the merge/rebase. Stage everything and commit. If rebasing, continue the rebase process until all commits are rebased.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.