resolve

resolve is a command for Claude Code from synaptiai/synapti-marketplace. It costs 38 tokens per session (2,475 once invoked), scanned A, original, Apache-2.0.

A workflow for finding and resolving merge conflicts on a branch or pull request. A merge conflict happens when Git cannot safely combine competing changes to the same code.

In plain words
What is it for?
Use it during an interrupted merge or rebase, or to resolve conflicts between a pull request or branch and the default branch.
Why use it?
It classifies the conflicts, applies an appropriate resolution, and checks whether the result still builds and passes tests.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool; mentions Claude Code.

Part of the flow plugin — 31 skills, 21 commands, 9 agents shipped together

Good fit Use it during an interrupted merge or rebase, or to resolve conflicts between a pull request or branch and the default branch.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/synaptiai/synapti-marketplace/resolve
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/synaptiai/synapti-marketplace

Made for: Claude Code.

Or install flow, the plugin that ships this one along with the rest of its 31 skills, 21 commands, 9 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for resolve

README.md
[![agentmods](https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/resolve.svg)](https://agentmods.dev/commands/synaptiai/synapti-marketplace/resolve)
Your own site
<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/resolve"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/resolve.svg" alt="Measured on agentmods" height="20"></a>
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,475 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.02475
Opus 5 $0.00019 $0.01238
Sonnet 5 $0.00008 $0.00495
Haiku 4.5 $0.00004 $0.00248

Measured 4d ago against content hash 7bf22c8c0df1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

resolve scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/flow/commands/resolve.md · 272 lines

How it starts

The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Resolve Merge Conflicts

4-phase EXPLORE > PLAN > CODE > VERIFY workflow for merge conflict resolution.

Required Skills

  • merge-conflict-resolution — conflict detection, classification, and resolution strategies
  • capability-discovery — discover build/test/lint commands
  • debugging-patterns — on-demand if resolution breaks the build

References

  • references/escalation-format.md — canonical six-field structure used by the max-conflict-files escalation (Phase 1) and any semantic/structural/delete-modify escalation surfaced during resolution

Phase 0: Pre-Flight

Determine invocation mode from $ARGUMENTS:

  1. No args + active conflict markers → resolve in-progress merge/rebase
  2. PR number → fetch PR, attempt merge against base, resolve conflicts
  3. Branch name → resolve conflicts for that branch against default branch

Validation

# Take the first whitespace-separated token; accept only if it matches the
# safe set [a-zA-Z0-9._/-] (covers digit-only PR numbers AND typical branch
# names like `feature/foo-bar.v2`). A token containing shell metacharacters
# (`;`, `|`, `$`, spaces, etc.) is rejected with empty RESOLVE_TARGET so the
# trailing context can't reach downstream shell. Trailing prose after the
# first whitespace is fine.
#
# Output: `###`-headed sections + KEY=value per
# `references/command-output-format.md`.
_RAW="$ARGUMENTS"  # Claude Code substitutes the bare arg token, not bash parameter-expansion
ARG1="${_RAW%% *}"
case "$ARG1" in
  ''|*[!a-zA-Z0-9._/-]*) RESOLVE_TARGET="" ;;
  *) RESOLVE_TARGET="$ARG1" ;;
esac

echo "### Resolve Mode"
# Quote parenthesized fallback per command-output-format.md rule 2.
echo "RESOLVE_TARGET=${RESOLVE_TARGET:-\"(none — in-progress merge mode)\"}"
if [ -f .git/MERGE_HEAD ] || [ -d .git/rebase-merge ] || [ -d .git/rebase-apply ]; then
  echo "CONFLICT_STATE=active"
else
  echo "CONFLICT_STATE=inactive"
fi

true

Read the full file on GitHub · 272 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 272 lines · 0 tokens per session scan A 7bf22c8c0df1

Subscribe to this mod's changes

resolve is a command published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 2,475 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.