agentmods.dev

merge

A command that moves completed work from a feature branch into the project's develop branch through a pull request. A feature branch is a separate line of work, and a pull request is a reviewable request to merge it.

In plain words
What is it for?
Use it to check the README and changelog, commit the current feature, push it, open a pull request to develop, and enable automatic merging when the repository allows it.
Why use it?
It gathers the required documentation checks and branch rules into one release-to-development workflow. This reduces the risk of merging from the wrong branch or skipping the project's version and changelog steps.

Command for Claude Code

72 3d ago A scan 23 tokens original Apache-2.0
View the source file flupkede/codesearch
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/flupkede/codesearch/merge
Clone the repo
git clone --depth 1 https://github.com/flupkede/codesearch

Made for: Claude Code.

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,348 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.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.01348
Opus 5 $0.00012 $0.00674
Sonnet 5 $0.00005 $0.00270
Haiku 4.5 $0.00002 $0.00135

Measured 2d ago against content hash 3f90a1d77477, 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.

.claude/commands/merge.md · 92 lines

How it starts

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

/merge — land the current feature branch on develop

Run the project's merge workflow: verify docs are current, then bring the current feature branch into develop through a pull request. This command does not tag a release — tagging happens only in /release.

Branch & version facts (this repo)

  • Flow: feature/* | features/* | fix/* → PR → develop → (later) PR → master.
  • master is protected (.github/workflows/protect-master.yml): it accepts PRs only from develop or release/*.
  • The pre-commit hook bumps the patch version (+1) and rebuilds the binary on feature branches only (feature/*, features/*, fix/*). On develop/master/release/chore it runs cargo fmt only — no bump. So the feature-branch commit here fixes the release version; it carries forward unchanged through develop, master, and the tag.

Guardrails

  • ABORT unless the current branch matches feature/*, features/*, or fix/* — i.e. the branches the pre-commit hook version-bumps. Never run from develop, master, release/*, or chore/*: on those the hook does not bump, so the version/CHANGELOG premise below would silently break.
  • NEVER push directly to develop or master — everything lands via a PR.
  • NEVER pass --no-verify / --no-gpg-sign — let the pre-commit hook run (it bumps + rebuilds).
  • Do NOT create or push a tag here. That is /release's job.
  • Do NOT force-push.

Steps

  1. Context

    • git rev-parse --abbrev-ref HEAD → current branch. If it is NOT feature/*, features/*, or fix/*, STOP with an error (see Guardrails).
    • git fetch origin.
    • Compute the change set landing on develop: git log origin/develop..HEAD --oneline plus git status --short for uncommitted work. If there is nothing to land, report and STOP.

  2. README up to date?

    • Inspect the change set for user-facing changes: new/removed CLI flags or subcommands, behavior changes, new env vars, new supported languages, new MCP tools.
    • Compare against README.md. If anything is missing, wrong, or stale, UPDATE README.md so it matches reality. Keep examples free of hardcoded config strings (per CLAUDE.md).
    • If README already matches, state that and move on.

Read the full file on GitHub · 92 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. 2d ago First seen · 92 lines · 23 tokens per session scan A 3f90a1d77477

Subscribe to this mod's changes

merge is a command published in the GitHub repository flupkede/codesearch (72 stars, last pushed 3d ago), licensed Apache-2.0. It adds 23 tokens to every session and 1,348 once invoked, about $0.0001 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-30.

Code reviewGit and workflowWriting and docsclaude-codecode-searchembeddingslocal-aimcpmcp-server
Related

Other commands, from other repositories

rp-build-cli

Build with rp-cli context builder → chat → implement.

gmickel/gno · 10 tokens

rp-investigate-cli

Deep codebase investigation and architecture research with rp-cli commands.

gmickel/gno · 11 tokens

rp-oracle-export-cli

Export context for oracle consultation using rp-cli.

gmickel/gno · 8 tokens

rp-reminder-cli

Continue your current workflow using rp-cli instead of built-in alternatives.

gmickel/gno · 5 tokens

call-graph

Trace callers, callees, or paths using the call graph.

Helweg/open-codebase-index · 12 tokens

index

Index the codebase for semantic search.

Helweg/open-codebase-index · 7 tokens