A Git merge command that combines one branch’s changes into another and creates a Conventional Commits message, a standard format for describing software changes. It can also process repositories inside subdirectories.

Use it to merge source and target branches, attach issue or specification references, request confirmation or skip it, and merge across several nested repositories.

It reduces the manual work of choosing branches, preparing the merge message, and repeating the operation across multiple repositories.

merge — Command by shdennlin

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.

agentmods

npx agentmods add commands/shdennlin/agent-plugins/merge

Clone the repo

git clone --depth 1 https://github.com/shdennlin/agent-plugins

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 981 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00009	$0.00981
Opus 5	$0.00005	$0.00491
Sonnet 5	$0.00002	$0.00196
Haiku 4.5	$0.00001	$0.00098

Measured 2d ago against content hash ca256124216e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

merge 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 2d 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/git-workflow/commands/merge.md · 114 lines

How it starts

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

Git Merge Command

Merge branches with a consolidated Conventional Commits merge message.

Arguments

Parse the following from $ARGUMENTS:

[source] - Optional: source branch to merge (1st positional arg). Defaults to current branch.
[target] - Optional: target branch to merge into (2nd positional arg). Defaults to develop if exists, else main.
--issue or -i - Optional: issue ID to include in commit message (e.g., #123, PROJ-456)
--spec or -s - Optional: spec name to include in commit message
--all - Scan subdirectories for git repos and merge each
--yes or -y - Skip confirmation prompt
--help or -h - Show usage information and exit

Instructions

Step 1: Parse Arguments

From $ARGUMENTS, extract:

help: if --help or -h is present, show the usage information below and stop. Do NOT delegate to the agent.
positional args: collect all arguments that don't start with -- or - (and aren't values for flags). First = source, second = target.
issue: value after --issue or -i
spec: value after --spec or -s
all: boolean, true if --all present
yes: boolean, true if --yes or -y present

Help Output

If --help or -h is present, display this and stop:

Usage: /git-workflow:merge [source] [target] [options]

Merge branches with auto-generated Conventional Commits message.

Positional arguments:
  source              Source branch to merge (default: current branch)
  target              Target branch to merge into (default: develop or main)

Options:
  -i, --issue <id>    Issue ID to reference in commit message (e.g., #123)
  -s, --spec <name>   Spec name to mention in commit message
  --all               Merge across all git repos in subdirectories
  -y, --yes           Skip confirmation prompt
  -h, --help          Show this help message

Examples:
  /git-workflow:merge                              Merge current branch into develop/main
  /git-workflow:merge feature/auth                 Merge feature/auth into develop/main
  /git-workflow:merge develop main                 Merge develop into main
  /git-workflow:merge -i "#123" -s auth-flow       With issue and spec references
  /git-workflow:merge develop main -y              Merge without confirmation
  /git-workflow:merge --all                        Merge across all sub-repos

Read the full file on GitHub · 114 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.

2d ago First seen · 114 lines · 9 tokens per session scan A ca256124216e

Subscribe to this mod's changes

merge is a command published in the GitHub repository shdennlin/agent-plugins (2 stars, last pushed 8d ago), licensed MIT. It adds 9 tokens to every session and 981 once invoked, about $0.0000 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-08-31.

Commits Git and workflow

merge

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Git Merge Command

Arguments

Instructions

Step 1: Parse Arguments

Help Output

What this file has done since we first saw it

Other commands, from other repositories

git-pr-push

gen-commit-msg

commit-all

commit

restart

summarize-changes