Borrowing it
Nothing to install: this file belongs to akiojin/unity-editor-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/akiojin/unity-editor-mcp/main/.claude/commands/merge-develop.mdgit clone --depth 1 https://github.com/akiojin/unity-editor-mcpWrote 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.
[](https://agentmods.dev/commands/akiojin/unity-editor-mcp/merge-develop)<a href="https://agentmods.dev/commands/akiojin/unity-editor-mcp/merge-develop"><img src="https://agentmods.dev/badge/commands/akiojin/unity-editor-mcp/merge-develop/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/akiojin/unity-editor-mcp/merge-develop"><img src="https://agentmods.dev/badge/commands/akiojin/unity-editor-mcp/merge-develop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00000 | $0.00861 |
| Opus 5.5 | $0.00000 | $0.00344 |
| Sonnet 5.5 | $0.00000 | $0.00172 |
| Haiku 4.5 | $0.00000 | $0.00086 |
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 2mo 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.
What it actually says
/merge-develop
最新のdevelopブランチを現在のブランチにマージするコマンド
概要
このコマンドは、リモートの最新のdevelopブランチを現在作業中のブランチにマージします。 CLAUDE.mdの基本ルールに従い、PR作成前に必ず実行する必要があります。
処理内容
-
現在のブランチ状態を確認
- 未コミットの変更がないかチェック
- 現在のブランチ名を取得
-
リモートの最新状態を取得
git fetch origin developで最新のdevelopブランチを取得
-
developブランチをマージ
git merge origin/developでマージ実行- コンフリクトがある場合は解決を促す
-
結果報告
- マージ成功時:成功メッセージを表示
- コンフリクト発生時:解決方法を案内
実行手順
#!/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する必要があります
- コンフリクトが発生した場合は、手動で解決する必要があります
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.
- 2mo ago First seen · 88 lines · 0 tokens per session scan A 66a8b01c6739
merge-develop is a command published in the GitHub repository akiojin/unity-editor-mcp (11 stars, last pushed 1y 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.
Other commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.