Resolving Merge Conflicts
Use when you need to resolve an in-progress git merge/rebase conflict.
Install
$ agentstack add skill-toverux-grimoire-resolving-merge-conflicts ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
- 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, and check any specs in docs/specs/ behind each change.
- 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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: toverux
- Source: toverux/grimoire
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.