agentsclimarketplace

Resolving merge conflicts

Skill stevennitesh/programming-agent-skills/skills/custom/resolving-merge-conflicts

Practical workflow skills for coding agents: scope, debugging, cleanup, subagents, GitHub tracking, and verification.

Install
npx -y skills add stevennitesh/programming-agent-skills --skill resolving-merge-conflicts

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Reconcile an in-progress merge, rebase, cherry-pick, revert, or conflict-marked file when the user asks to resolve conflicts. For status, explanation, or review, perform only read-only State and Trace.

SKILL.md

3.6 KB, 689 tokens by cl100k_base, as published. Nobody here has run it

Resolving Merge Conflicts

Treat every conflict as a three-way merge: base, both sides, and the operation goal.

Read-only: State -> Trace -> Return.

Reconcile: State -> Trace -> Reconcile -> Prove -> Return; add Finish before Return only with finish authority.

Reconciliation authority permits resolving requested in-scope conflicts. Finish authority separately permits staging and continuing the Git operation. The user request or owning caller packet grants them separately; invocation alone grants neither.

Process

  1. State. Read repo instructions and docs/agents/engineering-contract.md when present. Inspect git status, operation metadata, git ls-files -u, markers, dirty and index state, operation goal, scope, and both authorities. Identify the operation or marker-only state before mutation.
  2. Trace. Inspect the available base and both sides for every in-scope conflict; build the Source Trace for each intent. Map index stages to their actual roles. During rebase, ours is the so-far rebased target and theirs is the commit being replayed. Unproven required intent blocks that path.

Without reconciliation authority, stop after State and Trace. Report uncertainty and exact remaining state; leave files, index, commits, and Git-operation state unchanged.

  1. Reconcile. Resolve every in-scope content or path conflict. Preserve compatible intents; where incompatible, follow the Source Trace, operation goal, and commitment boundary, then record the trade-off. Keep only traced behavior. Inspect each full resolved file and rescan for markers.
  2. Prove. Run focused repo-owned checks and any broader canonical checks required by risk or repo convention. If proof fails, invoke $diagnosing-bugs in diagnosis mode and resume here with its causal packet. Repair only within the granted reconciliation scope; otherwise return blocked with the required scope or authority. Focused resolution proof must pass before Finish; broader skipped or proven pre-existing failures may remain explicit residual risk.
  3. Finish. With finish authority, block unrelated index state from the commit, stage only resolved in-scope paths, and continue the operation. Each new conflict returns to State until Git exits or a blocker remains. Without finish authority, leave staging, commit, and continuation untouched. Stage or commit marker-only work only when separately requested.

Guardrails

Abort, hard reset, or side discard requires explicit approval. Use wholesale --ours or --theirs only when the Source Trace proves the other side obsolete. Preserve unrelated dirty work and existing index state.

Return

Report the operation and goal, both authorities, inspected/resolved/blocked paths, intent trade-offs, proof and residual risk, current git status, and the finished operation or exact next command.

Completion

Read-only work completes after State and Trace are reported with exact remaining state and no mutation.

Reconciliation completes only when every in-scope entry and marker is resolved; each resolution has three-way trace and full-file inspection; focused resolution proof passes; unrelated work is preserved; and Git is finished only under finish authority or handed off in exact remaining state. A blocked path or unresolved resolution-caused failure returns a blocked outcome, never completion.

What ships with it: 1 file

42 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.