git-converge
Skill1 starsChanged 8 days agoApache-2.0View on GitHub
收敛分支(仅显式调用,写操作);/git-converge BRANCH [--apply] [--discard-ignored] [--help].
- Reads credentials
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- multi-agent-git-orchestratorSkill
- git-analyzeSkill
- git-cleanupSkill
- git-integrateSkill
- git-orchestratorSkill
- git-planSkill
- git-protectSkill
- git-recommendSkill
- git-reconSkill
- git-sweepSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 24
Default: Preview the merge plan, blocked items, and the expected final branch list, with every failed gate and blocker followed by the …
- Very specific: line 54
Do not use commands/*.md for this adapter.
- Very specific: line 56
If ../../SKILL.md or ../../references/commands.md cannot be read, name the missing path, report that the MAGOS installation is incomplete, …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
GitConverge
Command adapter for the canonical /GitConverge command of the MAGOS (Multi-Agent Git Orchestrator) package. Use it only when the user explicitly invokes /git-converge in Hermes or $git-converge in Codex.
Usage
- Hermes:
/git-converge <branch> [--apply] [--discard-ignored] [--lang <language>] [--help] - Codex:
$git-converge <branch> [--apply] [--discard-ignored] [--lang <language>] [--help] <branch>: Required local branch that receives everything. Matched exactly (case-sensitive); it must not bemain.--apply: Merge every local branch's unique commits (mainfirst) into<branch>, then delete the merged local branches and their clean worktrees so onlymainand<branch>remain. A conflict stops the command and deletes nothing. It never moves or deletesmainand never touches remote branches.--discard-ignored: With--apply, also allow removing worktrees that hold ignored files (for example.env). Without it those worktrees and their branches are kept.--lang <language>: Language of the reply, as a name or code (for exampleEnglish,ja); Chinese when absent. Command names, options, branch names, paths, SHAs, and status codes stay untranslated.--help: Show this inline usage and argument description, then stop without inspecting or changing the repository.- Default: Preview the merge plan, blocked items, and the expected final branch list, with every failed gate and blocker followed by the action that lifts it; nothing is changed.
Examples: /git-converge agent/release, $git-converge agent/release --apply, $git-converge <branch> --lang English, $git-converge --help.
Arguments
- Codex: the arguments are the text that follows
$git-convergein the user's message. - Plugin installs prefix the name with the plugin name:
/magos:git-convergein Hermes,$magos:git-convergein Codex; Claude Code hides this adapter and offers the command/magos:GitConvergeinstead. The arguments follow the name the same way. - Hermes: the arguments are the instruction Hermes appends after the skill content, introduced by "The user has provided the following instruction alongside the skill invocation:" (single command) or
User instruction:(stacked commands). An empty instruction means no arguments.
If --help is present, even with other arguments, answer from the inline Usage section above and stop before any tool call, file read, or repository inspection. If the branch is missing, show this help and ask for it; for an unknown option, explain the error and show this help. Do not inspect or change the repository in these error cases. Read the shared files below only for a normal invocation.
Explicit invocation only
A semantic match or automatic skill selection is not authorization to write. Claude Code keeps the model from invoking this adapter through disable-model-invocation: true in its frontmatter, and Codex disables implicit selection for it through agents/openai.yaml; Hermes has no per-skill switch, so this rule applies there by instruction. An explicit invocation is the user's /git-converge command (Hermes renders it as "The user has invoked the "git-converge" skill" followed by the arguments) or $git-converge in Codex. With a plugin install, the user's /magos:git-converge (Hermes) or $magos:git-converge (Codex) is the same explicit invocation; Claude Code hides this adapter, and there the user's /magos:GitConverge command is the explicit invocation. If this adapter was selected without such an invocation, preview at most and merge and delete nothing.
Shared files
This adapter belongs to the MAGOS package. The shared files are in the package root, two directories above this skill's directory:
../../SKILL.md: shared orchestration rules and safety invariants.../../references/commands.mdsection 6. GitConverge: command contract, classifications, gates, and apply procedure.../../references/reconnaissance.mdand../../references/decision-matrix.md: inspection steps and cleanup criteria.
Locate them as follows:
- Codex: resolve the paths relative to the directory that contains this
SKILL.md. - Hermes: take the absolute path from the
[Skill directory: ...]line (when the skill was loaded withskill_viewinstead of a slash command, from theskill_dirfield it returns), go up two directories, and read the files with the file or terminal tool. The skill viewer rejects paths that contain... Alternatively, load the skillmulti-agent-git-orchestrator(magos:git-orchestratorunder a Hermes plugin install) and view its files underreferences/. - Other hosts: resolve the paths relative to this file.
Do not use commands/*.md for this adapter. Those files are Claude Code slash-command wrappers with Claude-specific loading steps.
If ../../SKILL.md or ../../references/commands.md cannot be read, name the missing path, report that the MAGOS installation is incomplete, and do not merge, switch, or delete anything; a read-only preview is still allowed.
Execution
Execute the canonical /GitConverge command only when the user explicitly invoked this command skill. Preview by default; merge and delete only when the explicit command includes --apply and every gate still passes, and record the full plan first (every local branch with its tip, merge status and blockers, the merge order, and the expected final branches) and include it in the final report. Stop on a conflict and delete nothing. Never push, force-push, or delete remote branches; never use git branch -D or git worktree remove --force; never run a repository-wide git worktree prune. Git commands run as argument lists, never as shell strings, and a source branch (any local branch other than main and <branch>) whose name holds a character outside ASCII letters, ASCII digits and . _ / + -, or starts with - or +, is UNKNOWN and is never passed to a command. Ask for a branch if none is provided. Reply in the language selected by --lang (Chinese when absent); never translate commands, options, branch names, paths, SHAs, or status codes. Remove --lang and its value from the arguments before parsing the rest.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

