metagit-control-center
Skill4 starsChanged 13 days agoMITView on GitHub
Use when running metagit as an MCP control center for multi-repo awareness, guarded sync, and operational knowledge across ongoing agent tasks.
In this repository62 other files it gives its agents.
- agentsAGENTS.md
- docs/agents.mdAGENTS.md
- agentsAGENTS.md
- agentsCopilot instructions
- .cursor/rules/github-cli.mdcCursor rule
- .cursor/rules/project-level.mdcCursor rule
- llms.txtllms.txt
- gitnexus-cliSkill
- gitnexus-debuggingSkill
- gitnexus-exploringSkill
- gitnexus-guideSkill
- gitnexus-impact-analysisSkill
- gitnexus-refactoringSkill
- humanizerSkill
- metagit-agent-accessSkill
- metagit-agent-coordinationSkill
- metagit-aosSkill
- metagit-bootstrapSkill
- metagit-campaignSkill
- metagit-cliSkill
- metagit-config-refreshSkill
- metagit-context-packSkill
- metagit-control-centerSkill
- metagit-gatingSkill
- metagit-gitnexusSkill
- metagit-graph-maintainSkill
- metagit-mcp-resourcesSkill
- metagit-multi-repoSkill
- metagit-projectsSkill
- metagit-release-auditSkill
- metagit-repo-impactSkill
- metagit-rewrite-campaignSkill
- metagit-sharing-stateSkill
- metagit-stampSkill
- metagit-upstream-scanSkill
- metagit-upstream-triageSkill
- metagit-workspace-scopeSkill
- metagit-workspace-syncSkill
- metagit-agent-accessSkill
- metagit-agent-coordinationSkill
- metagit-aosSkill
- metagit-bootstrapSkill
- metagit-campaignSkill
- metagit-cliSkill
- metagit-cliSkill
- metagit-config-refreshSkill
- metagit-context-packSkill
- metagit-gatingSkill
- metagit-gitnexusSkill
- metagit-graph-maintainSkill
- metagit-mcp-resourcesSkill
- metagit-multi-repoSkill
- metagit-projectsSkill
- metagit-release-auditSkill
- metagit-repo-impactSkill
- metagit-rewrite-campaignSkill
- metagit-sharing-stateSkill
- metagit-stampSkill
- metagit-upstream-scanSkill
- metagit-upstream-triageSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 10 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Use this skill when an agent should actively coordinate repository context and task execution across a workspace.
- Distinctive: line 39
Use when skill scripts are unavailable (Hermes SKILL-only install, no shell helpers):
- Very specific: line 54
Run context pack + session prompt first (see metagit-context-pack skill):
- Very specific: line 62
Read metagit://workspace/config and metagit://workspace/repos/status (MCP) or tier-1 pack JSON (CLI).
- Very specific: line 63
Call metagit_project_context_switch when the objective is tied to a workspace project.
- Very specific: line 64
Run metagit_workspace_health_check or read metagit://workspace/health for maintenance signals.
- Distinctive: line 69
Use workspace search and upstream hints before broad exploration.
- Very specific: line 73
Default to fetch for visibility.
- Very specific: line 74
Use pull or clone only with explicit permission and rationale.
- Very specific: line 78
Before switching projects: metagit_session_update (notes + recent repos), optional metagit_workspace_state_snapshot.
- Very specific: line 79
After returning: metagit_workspace_state_restore when a snapshot was taken (metadata only.
- Distinctive: line 89
When delegating single-repo or specialist work:
- Distinctive: line 107
Use metagit search first when blocker appears external to current repo.
- Distinctive: line 108
Prefer deterministic evidence over speculative jumps.
- Distinctive: line 109
Keep operations minimal and auditable.
- Distinctive: line 121
Never mutate repositories without explicit authorization.
- Distinctive: line 122
Never broaden scope beyond configured workspace boundaries.
- Distinctive: line 123
Always preserve a clear audit trail of control actions.
≈ “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
Metagit Control Center Skill
Use this skill when an agent should actively coordinate repository context and task execution across a workspace.
Purpose
Provide a repeatable control-center workflow where Metagit MCP guides awareness, synchronization, and operational continuity over multiple related repositories.
Bundled scripts (optional)
Helper scripts live under scripts/ when the full skill tree is installed. Hermes
skill_manage copies SKILL.md only — scripts are not present unless you also run
metagit skills install --skill metagit-control-center.
Resolve scripts from the PyPI package (works whenever metagit-cli is installed):
SKILL_ROOT="$(python3 -c "import metagit, pathlib; print(pathlib.Path(metagit.__file__).parent / 'data/skills/metagit-control-center')")"
"$SKILL_ROOT/scripts/control-cycle.sh" [root_path] ["query"] [preset]Or from a full skill install:
"${HERMES_HOME:-$HOME/.hermes}/skills/metagit-control-center/scripts/control-cycle.sh" .Wrapper behavior:
- runs gating status first
- optionally runs upstream discovery for blocker queries
- emits compact, machine-readable lines
Inline CLI fallback (no scripts)
Use when skill scripts are unavailable (Hermes SKILL-only install, no shell helpers):
export METAGIT_AGENT_MODE=true
metagit mcp serve --status-once --root .
metagit context pack --tier 1 --json -c .metagit.yml
metagit prompt workspace -k health-preflight --text-only -c .metagit.yml
# blocker may be upstream — search managed repos:
metagit search "error signature" -c .metagit.yml --json
metagit prompt workspace -k sync-safe --text-only -c .metagit.ymlCore Workflows
1) Session Initialization
- Run context pack + session prompt first (see
metagit-context-packskill):
metagit context pack --tier 2 --json -c .metagit.yml
metagit prompt workspace -k session-start --text-only -c .metagit.yml- Validate active workspace gate (
metagit mcp serve --status-onceor gate script). - Read
metagit://workspace/configandmetagit://workspace/repos/status(MCP) or tier-1 pack JSON (CLI). - Call
metagit_project_context_switchwhen the objective is tied to a workspace project. - Run
metagit_workspace_health_checkor readmetagit://workspace/healthfor maintenance signals. - Identify stale repos and unresolved blockers from prior activity.
2) Active Task Support
- For each coding objective, map impacted repos.
- Use workspace search and upstream hints before broad exploration.
- Sync only repos that are required by the active objective.
3) Guarded Synchronization
- Default to
fetchfor visibility. - Use
pullorcloneonly with explicit permission and rationale. - Track sync outcomes in operations log resource.
4) Operational Memory
- Before switching projects:
metagit_session_update(notes + recent repos), optionalmetagit_workspace_state_snapshot. - After returning:
metagit_workspace_state_restorewhen a snapshot was taken (metadata only; git tree is unchanged).
Maintain bounded local records of:
- sync actions
- issue signatures searched
- candidate upstream repos identified
- unresolved dependencies and follow-ups
5) Subagent dispatch loop
When delegating single-repo or specialist work:
- Route —
metagit agent list --jsonor MCPmetagit_agent_catalog; picktemplate_idfromdelegates_to. - Plan —
metagit agent dispatch-plan <id> --project P --repo R --vendor V --jsonor MCPmetagit_agent_dispatch_plan. - Profile — when JSON includes
profile_apply_command, run it (ormetagit agent apply …) before launch.<!-- modality:agent_profile_apply --><!-- modality:dispatch_profile_capabilities --> - Ensure — run
install.commandonce wheninstall.neededis true. - Hand off — run
handoff.context_packandhandoff.prompt; passhandoff.effective_instructionsto the subagent. - ACL isolation (optional) — when
handoff.acl_commandsis present, follow skillmetagit-agent-coordination(allocate → lease → worktree → claim) so agents never share checkouts.<!-- modality:acl_branch --><!-- modality:acl_lease --><!-- modality:acl_worktree --><!-- modality:acl_claim --><!-- modality:acl_manifest -->ACL branch leases ≠ handoff claim TTL. Doc:docs/reference/agent-coordination.md. - Reconcile —
metagit_session_updateafter the subagent returns; respectout_of_scopeboundaries.
metagit agent dispatch-plan repo-implementer \
--project my-api --repo backend --vendor cursor --jsonDecision Guidelines
- Use metagit search first when blocker appears external to current repo.
- Prefer deterministic evidence over speculative jumps.
- Keep operations minimal and auditable.
Output Contract
For each control-center cycle, provide:
- current objective
- repositories examined
- actions taken (or intentionally deferred)
- next recommended step
Safety Rules
- Never mutate repositories without explicit authorization.
- Never broaden scope beyond configured workspace boundaries.
- Always preserve a clear audit trail of control actions.
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.

