원클릭으로
meta-safety
Multi-repo safety discipline — precision operations, dependency checking, and efficiency tips.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Multi-repo safety discipline — precision operations, dependency checking, and efficiency tips.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Safety check before refactoring - shows callers, callees, and impact analysis
Explore codebase semantically - find relevant code and documents using natural language search
Manage GitKB knowledge base for project documentation, tasks, and context. Use when working with KB documents, viewing tasks, updating progress, or managing project knowledge.
Understand a file or symbol's structure and dependencies using code intelligence tools
Manage isolated git worktree sets for multi-repo tasks.
Execute commands across all repos — parallel, filtered, dry-run modes.
| name | meta-safety |
| description | Multi-repo safety discipline — precision operations, dependency checking, and efficiency tips. |
Multi-repo workspaces are powerful but require awareness. Meta gives you precision tools to operate on exactly what you need, saving turns and avoiding unintended changes.
meta project list --json — workspace map in one callmeta git status — see state of all repos at once.meta.yaml for provides/depends_on)Instead of cd-ing into repos one by one, use meta flags to target exactly what you need:
# Target specific repos
meta --include repo1,repo2 exec -- command
# Target by tag
meta --tag backend exec -- cargo test
# Exclude repos
meta --exclude legacy exec -- npm update
# Dependency-aware order
meta --ordered exec -- cargo build
# Combine: tagged repos, in order, excluding one
meta --tag backend --exclude legacy --ordered exec -- make deploy
When modifying a repo that other repos depend on:
meta_analyze_impact <repo-name> (MCP tool) to see transitive dependentsmeta_core changes, repos that depend on it may need updatesmeta --ordered exec -- cargo build respects the dependency graph# Commit in exactly the repos you modified
meta --include repo1,repo2 git commit -m "feat: update shared API"
# Push only tagged repos
meta --tag backend git push
# Per-repo commit messages (when changes differ)
# Use meta_git_multi_commit MCP tool
The meta_query_repos MCP tool filters repos by state:
| Query | Result |
|---|---|
dirty:true | Repos with uncommitted changes |
tag:backend | Repos tagged "backend" |
dirty:true AND tag:backend | Combine filters |
branch:feature-x | Repos on a specific branch |
meta git status replaces N individual git status callsmeta --tag X exec -- cmd replaces N cd && cmd sequencesmeta_analyze_impact before modifying providers prevents cascading fix-up commitsmeta --ordered exec -- cargo build builds in correct dependency order automaticallymeta --dry-run exec -- dangerous-cmd previews before executing