merge-develop

A command that brings the latest remote `develop` branch into the branch you are currently working on. A branch is a separate line of code changes, and `develop` is commonly used for shared ongoing work.

In plain words
What is it for?
Use it before opening a pull request to update a feature branch from `origin/develop` and check whether conflicts need resolving.
Why use it?
It helps reveal conflicts and incompatibilities before creating a pull request. It stops when the branch is `main` or `develop`, or when uncommitted changes could make the merge unsafe.

Command for Claude Code

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/akiojin/unity-editor-mcp/merge-develop
Clone the repo
git clone --depth 1 https://github.com/akiojin/unity-editor-mcp

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 861 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.00000 $0.00861
Opus 5 $0.00000 $0.00430
Sonnet 5 $0.00000 $0.00172
Haiku 4.5 $0.00000 $0.00086

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

Security

Grade A, and why

merge-develop 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-develop.md · 88 lines

What it actually says

/merge-develop

最新のdevelopブランチを現在のブランチにマージするコマンド

概要

このコマンドは、リモートの最新のdevelopブランチを現在作業中のブランチにマージします。 CLAUDE.mdの基本ルールに従い、PR作成前に必ず実行する必要があります。

処理内容

  1. 現在のブランチ状態を確認

    • 未コミットの変更がないかチェック
    • 現在のブランチ名を取得
  2. リモートの最新状態を取得

    • git fetch origin develop で最新のdevelopブランチを取得
  3. developブランチをマージ

    • git merge origin/develop でマージ実行
    • コンフリクトがある場合は解決を促す
  4. 結果報告

    • マージ成功時:成功メッセージを表示
    • コンフリクト発生時:解決方法を案内

実行手順

#!/bin/bash

# 現在のブランチ名を取得
current_branch=$(git branch --show-current)
echo "現在のブランチ: $current_branch"

# mainまたはdevelopブランチでの直接マージを防ぐ
if [[ "$current_branch" == "main" ]] || [[ "$current_branch" == "develop" ]]; then
    echo "❌ エラー: mainまたはdevelopブランチでの直接マージは禁止されています"
    exit 1
fi

# 未コミットの変更をチェック
if [[ -n $(git status --porcelain) ]]; then
    echo "⚠️  警告: 未コミットの変更があります"
    echo "マージ前にコミットまたはstashしてください"
    git status --short
    exit 1
fi

# リモートの最新developを取得
echo "📥 リモートの最新developブランチを取得中..."
git fetch origin develop

# マージ実行
echo "🔄 developブランチをマージ中..."
if git merge origin/develop; then
    echo "✅ developブランチのマージが完了しました"

    # マージコミット数を表示
    merged_commits=$(git rev-list --count HEAD...origin/develop)
    echo "📊 マージされたコミット数: $merged_commits"

    # 次のステップを案内
    echo ""
    echo "次のステップ:"
    echo "1. テストを実行して動作を確認"
    echo "2. 変更内容をプッシュ: git push origin $current_branch"
    echo "3. PRを作成または更新"
else
    echo "❌ マージ中にコンフリクトが発生しました"
    echo ""
    echo "コンフリクト解決の手順:"
    echo "1. コンフリクトのあるファイルを確認: git status"
    echo "2. 各ファイルのコンフリクトを解決"
    echo "3. 解決後: git add <ファイル名>"
    echo "4. すべて解決したら: git commit"
    echo ""
    echo "または、マージを中止する場合: git merge --abort"
fi

注意事項

  • CLAUDE.mdの基本ルールに従い、PR作成前には必ずdevelopの最新版をマージする必要があります
  • mainまたはdevelopブランチでの直接作業は禁止されているため、これらのブランチでは実行できません
  • 未コミットの変更がある場合は、マージ前にコミットまたはstashする必要があります
  • コンフリクトが発生した場合は、手動で解決する必要があります
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 · 88 lines · 0 tokens per session scan A 66a8b01c6739

Subscribe to this mod's changes

merge-develop is a command published in the GitHub repository akiojin/unity-editor-mcp (11 stars, last pushed 12mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 861 tokens. 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.