Discovering Workspace Scope

Use this skill at session start for workspace-aware tasks. Prefer metagit-context-pack for the full tiered pack workflow; this skill focuses on scope boundaries and Hermes wiring.

Do not dump the umbrella manifest. metagit workspace list --json is a paged index (no summary.workspace). Use --project on packs and workspace repo list --json --detail slim. 500+ repos: metagit prompt workspace -k large-workspace --text-only.

Workflow

1. Run context pack (tier 0 minimum, tier 2 at session open):

export METAGIT_AGENT_MODE=true
metagit context pack --tier 0 --json --project <name> -c .metagit.yml
metagit prompt workspace -k session-start --text-only -c .metagit.yml

2. Run workspace gate and status checks.
3. Build a compact map of active project names, repo names, and sync state from pack JSON.
4. Report a bounded scope for the current objective.

Hermes session bootstrap

Wire into Hermes (or any orchestrator) before the first tool call on a workspace task.

export METAGIT_AGENT_MODE=true
PACK_JSON="$(metagit context pack --tier 0 --json -c .metagit.yml)"
PROMPT_TEXT="$(metagit prompt workspace -k session-start --text-only -c .metagit.yml)"

Token-tight alternative: tier 0 pack + session-start prompt only.

See metagit-context-pack for tier escalation, objectives, approvals, and repomix.

Commands

Gate check (pick one):

SKILL_ROOT="$(python3 -c "import metagit, pathlib; print(pathlib.Path(metagit.__file__).parent / 'data/skills/metagit-gating')")"
"$SKILL_ROOT/scripts/gate-status.sh" [root_path]
# inline fallback:
metagit mcp serve --status-once --root .

Scope discovery:

metagit context pack --tier 1 --json --project <name> -c .metagit.yml
metagit workspace list -c .metagit.yml --json
metagit workspace repo list -c .metagit.yml --json --detail slim
metagit search "<query>" -c .metagit.yml --json --limit 10
cd "$(metagit search "<query>" -c .metagit.yml --path-only)"

Interactive (human sessions only):

• metagit nav / metagit navigate — FuzzyFinder project then repo, then open editor
• metagit nav --all — one picker of every managed project/repo (optional --unmanaged, --print-path)
• metagit workspace select --project <name>

Agent navigate (preferred over nav):

• metagit workspace repo list -c .metagit.yml --json --detail slim — MCP metagit_workspace_repos_list
• metagit search "<query>" --path-only — MCP metagit_repo_search {path_only: true}

Agent context switch (preferred):

• metagit context switch <project> [<repo>] — pack + prompt + objective + shell-eval env
• MCP metagit_context_switch — same envelope as JSON
• Lean MCP metagit_project_context_switch when pack/objective are not needed
• MCP metagit_workspace_state_snapshot before leaving a project for a long switch

Multi-instance workspaces (Syncthing)

When agents on multiple machines share a manifest via Syncthing:

1. Wait for sync idle, then metagit config validate before trusting scope.
2. Designate one writer for .metagit.yml catalog edits.
3. Only the session-owning agent runs context pack --tier 2 (updates session boundary).
4. Git clones are local — run metagit project sync per machine after manifest changes.
5. Check digest.manifest_changed after tier-2 pack if another agent may have edited the manifest.

Full conflict-avoidance table: metagit-context-pack skill.

Output Contract

Return:

• active/inactive workspace state and reason
• candidate project to operate on
• top repositories to inspect first (prioritize health flags from pack cards)

Safety

• Keep operations read-only in this step.
• Do not sync or mutate repositories without explicit request.