Metagit Control Center

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.yml

Core Workflows

1) Session Initialization

• Run context pack + session prompt first (see metagit-context-pack skill):

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-once or gate script).
• Read metagit://workspace/config and metagit://workspace/repos/status (MCP) or tier-1 pack JSON (CLI).
• Call metagit_project_context_switch when the objective is tied to a workspace project.
• Run metagit_workspace_health_check or read metagit://workspace/health for 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 fetch for visibility.
• Use pull or clone only with explicit permission and rationale.
• Track sync outcomes in operations log resource.

4) Operational Memory

• Before switching projects: metagit_session_update (notes + recent repos), optional metagit_workspace_state_snapshot.
• After returning: metagit_workspace_state_restore when 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:

1. Route — metagit agent list --json or MCP metagit_agent_catalog; pick template_id from delegates_to.
2. Plan — metagit agent dispatch-plan <id> --project P --repo R --vendor V --json or MCP metagit_agent_dispatch_plan.
3. Profile — when JSON includes profile_apply_command, run it (or metagit agent apply …) before launch.
4. Ensure — run install.command once when install.needed is true.
5. Hand off — run handoff.context_pack and handoff.prompt; pass handoff.effective_instructions to the subagent.
6. ACL isolation (optional) — when handoff.acl_commands is present, follow skill metagit-agent-coordination (allocate → lease → worktree → claim) so agents never share checkouts. ACL branch leases ≠ handoff claim TTL. Doc: docs/reference/agent-coordination.md.
7. Reconcile — metagit_session_update after the subagent returns; respect out_of_scope boundaries.

metagit agent dispatch-plan repo-implementer \
  --project my-api --repo backend --vendor cursor --json

Decision 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.