Metagit campaign skill
Use when coordinating many repos under one intent (rollout, migration, tier stamp) with a committed, diffable status overlay.
Docs: campaigns.md · campaign-everroom.md · Registry: modality-feature-registry.md
When to use
- One selection query → frozen repo list → per-repo status/MR tracking
- Fan-out spine objectives for parallel agents (
campaign expand) - Rollup: merged vs open MR vs blocked without manual spreadsheets
- Combined Campaign Context from MetaGit topology plus optional EverRoom evidence
Configuration
# metagit.config.yaml
workspace:
campaigns_path: _campaigns # default; or knowledge/campaigns
Env: METAGIT_WORKSPACE_CAMPAIGNS_PATH
Lifecycle
export METAGIT_AGENT_MODE=true
metagit campaign new --slug tier-full --title "Full-tier rollout" \
--query "platform" --tag agent_tier=full
metagit campaign validate
metagit campaign expand --slug tier-full --dry-run
metagit campaign expand --slug tier-full
metagit campaign set --slug tier-full --repo platform/api --status merged --mr "https://…"
metagit campaign status --slug tier-full --json --limit 40
--json on new/status/set/expand returns counts + a page, not the overlay YAML. Page with --offset. Freeze up to 2000 matches on disk; never paste _campaigns/*.yml into the conversation.
Board linking (Azure DevOps)
Pointer on the campaign or a repo row (provider, id, url, organization, project, kind). Tokens stay in AppConfig / METAGIT_AZURE_DEVOPS_*.
metagit campaign new --slug payments --title "Payments" --query payments \
--work-item azure_devops:12345 --json
metagit campaign board-sync --slug payments --organization myorg --ado-project platform \
--dry-run --json
metagit campaign board-sync --slug payments --organization myorg --ado-project platform \
--limit 40 --offset 0 --json
MCP: metagit_campaign_status, metagit_campaign_board_sync (dry_run: true first). Docs: context-reduction.md.
Campaign Context (optional EverRoom)
A campaign is the technical/work boundary. An EverRoom Room is the context/evidence boundary.
- MetaGit answers: "What exists and what is affected?"
- EverRoom answers: "What do we know, why did we decide it, and what context surrounds it?"
When operating on a campaign:
- Identify the campaign slug.
- Inspect MetaGit technical scope (
campaign status/campaign context). - Check whether an EverRoom provider is attached (
campaign everroom status). - Retrieve Campaign Context (
campaign context --jsonor MCPmetagit_campaign_context). - Use MetaGit for topology, Git state, and relationships.
- Use EverRoom for rationale, evidence, decisions, and historical context.
- Do not treat generated summaries as authoritative over source material.
- Cite
source=metagitvssource=everroom. - Do not retrieve unrelated Room/global context through MetaGit.
export METAGIT_EVERROOM_URL=http://127.0.0.1:3210
export METAGIT_EVERROOM_TOKEN=… # never put this in YAML, Git, or prompts
metagit campaign everroom attach --slug terraform-hcp-migration --room room_01J…
metagit campaign context --slug terraform-hcp-migration --json
metagit campaign everroom sync --slug terraform-hcp-migration
metagit campaign everroom detach --slug terraform-hcp-migration
If EverRoom is down, campaign context still returns MetaGit-only data with a warning. attach/sync fail instead of mutating blindly.
Never store tokens in _campaigns/*.yml. Room id ≠ campaign slug.
Agent posture before repo work
metagit agent profile show -p platform -n api --json
metagit agent apply --vendor claude_code --project platform --repo api
Orchestrator polling
metagit context events --campaign tier-full --since "<iso-cursor>" --json
Related skills
metagit-multi-repo·metagit-control-center·metagit-context-pack