Install any skill in seconds. Free to start, no credit card required.
Get Started Free →stevesolun/resolving-merge-conflicts
Resolve an in-progress Git merge or rebase conflict while preserving the relevant intent of both sides.
7 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 7 comparable cases; this report requires 8.
A test case the skill fixed. Same model, same prompt, with and without the skill.
I had conflicts in `config/database.yml` and `app/models/db.rb`. I asked you to fix them, test them, and complete the merge. What essential reporting elements should you provide in your final response?
| Checked | Without skill | With skill |
|---|---|---|
| The assistant states that reported details must include what was resolved. | Passed | Passed |
| The assistant states that reported details must include what was verified. | Passed | Passed |
| The assistant states that reported details must include any remaining uncertainty. | Missed | Passed |
The instructions your model reads when the skill loads.
Pause rather than guess when neither intent can be preserved safely. Aborting or restarting can be the correct recovery when the base is wrong, the operation is contaminated, or the user prefers a clean retry; explain the trade-off before taking that destructive step.
test cases passed with the skill
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.